Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3147

Update resteasy-jettison provider module support to deprecated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.0.0.ER7
    • 7.0.0.ER4
    • Modules, REST
    • None

    Description

      Make the module resteasy-jettison-provider deprecated in EAP.

      This is based on the discussion i email thread:

      ----- Original Message -----
      From: "Dimitris Andreadis" <dandread@redhat.com>
      To: "Katerina Novotna" <kanovotn@redhat.com>
      Cc: "Dimitris Andreadis" <dimitris@redhat.com>, "Weinan Li" <weli@redhat.com>, "Bill Burke" <bburke@redhat.com>, "Marek Kopecky" <mkopecky@redhat.com>, "Ron Sigal" <rsigal@redhat.com>, "Jason T. Greene" <jgreene@redhat.com>, "Stuart Douglas" <sdouglas@redhat.com>, "Bilgehan Ozpeynirci" <bilge@redhat.com>
      Sent: Tuesday, February 2, 2016 11:17:44 AM
      Subject: Re: Jettison provider not trigerred in EAP7

      (copying Bilge, too)

      In EAP6 I see:
      https://mojo.redhat.com/docs/DOC-1053168

      org.jboss.resteasy.resteasy-jackson-provider public
      org.jboss.resteasy.resteasy-jettison-provider public

      So we cannot just "remove" stuff. I think the right approach is to mark:

      org.jboss.resteasy.resteasy-jettison-provider deprecated

      And if it doesn't work for the user out of the box, make sure there is at least a workaround
      for existing applications to work.

      Please update DOC-1053168 and make a blocking JBEAP jira for updating the jettison-provider
      support level.

      Thanks

      /Dimitris

      Attachments

        Issue Links

          causes

          Task - Represents a small unit of work that is not end-user facing. WFLY-6236 Remove RTS dependency on resteasy-jettison-provider

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. WFLY-6232 Update resteasy-jettison provider module support to deprecated

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3087 Resteasy jettison provider commented out in the JaxrsDepependencyProcessor

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-2856 NoMessageBodyWriterFoundFailure when using NoJackson and json annotated resource

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3301 Migration guide - jettison provider deprecated

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3304 Development guide - jaxrs - json support

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              tomazcerar Tomaž Cerar (Inactive)
              kanovotn Katerina Odabasi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: