Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-801

RestEasy's default JSON provider is Jackson, contrary to documented Jetisson

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST
    • Labels:
    • Similar Issues:
      Show 10 results 

      Description

      RestEasy's docs state that the default JSON provider is Jettison.
      That should react to JAXB's @XmlTransient.

      But with default config, only {{@org.​codehaus.​jackson.​annotate.JsonIgnore}} works. Which means that Jackson is used.

      Not sure if it's intended. If so, please move this bug to RESTEASY, and it should be documented in "19.4. JAXB + JSON provider" that AS uses Jackson by default.

      Also note that in AS 7.1.3.CR1, RestEasy modules are private, so using Jackson's annotations needs users go to module.xml's and change this.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            ozizka Ondrej Zizka added a comment -

            Seems like it's actually a matter of AS documentation: It should provide a way to switch to different provider.
            RestEasy keeps doing what it says in docs - pick up Jackson if it's available. And since it is, it's used.
            So, we should describe here how to remove Jackson and let Jettison be used.

            Show
            ozizka Ondrej Zizka added a comment - Seems like it's actually a matter of AS documentation: It should provide a way to switch to different provider. RestEasy keeps doing what it says in docs - pick up Jackson if it's available. And since it is, it's used. So, we should describe here how to remove Jackson and let Jettison be used.
            Hide
            dougbateman Doug Bateman added a comment -

            Yeah, this is a documentation bug. I'm surprised it's marked "resolved-won't fix" when it's just a matter of fixing the docs.

            Show
            dougbateman Doug Bateman added a comment - Yeah, this is a documentation bug. I'm surprised it's marked "resolved-won't fix" when it's just a matter of fixing the docs.

              People

              • Assignee:
                swd847 Stuart Douglas
                Reporter:
                ozizka Ondrej Zizka
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development