Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5511

@JsonIgnore does not work on Fuse-6.2.1-on-EAP

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • None
    • None
    • % %
    • Hide

      1. Obtain the test project by cloning https://bitbucket.org/syddjurskommune/fusetest
      1a. Rename src/Test to src/test if you aren't using Windows
      2. Build the project
      3. Install EAP 6.4.0
      4. Install the Fuse module using the Fuse 6.2.1 EAP installer
      5. Deploy the compiled WAR by copying to standalone/deployments
      6. Start EAP standalone. Note that the test fails, with a long error message about a circular reference chain, followed by a stack overflow
      7. Run the unit test : "mvn test"
      8. Note that the test succeeds

      Show
      1. Obtain the test project by cloning https://bitbucket.org/syddjurskommune/fusetest 1a. Rename src/Test to src/test if you aren't using Windows 2. Build the project 3. Install EAP 6.4.0 4. Install the Fuse module using the Fuse 6.2.1 EAP installer 5. Deploy the compiled WAR by copying to standalone/deployments 6. Start EAP standalone. Note that the test fails, with a long error message about a circular reference chain, followed by a stack overflow 7. Run the unit test : "mvn test" 8. Note that the test succeeds
    • Sprint 5 - towards ER2

    Description

      The @JsonIgnore attribute applied to a data model attribute should prevent that attribute being rendered into JSON when using camel-jackson marshalling. This is sometimes necessary if the attribute cannot correctly be rendered (for example, as in the test case, it forms a circular reference).

      When a Camel route that marshalls to JSON is deployed on EAP 6.4.0, the @JsonIgnore attribute appears to have no effect. In a unit test, however (where, I presume, the artefacts will all match Fuse 6.2.1 versions) the attribute does what it is supposed to.

      I surmise that this problem is caused by some variance between the Jackson or other JSON bits in Fuse on EAP, compared to Fuse.

      Attachments

        Activity

          People

            jnethert@redhat.com James Netherton
            rhn-support-kboone Kevin Boone
            Viliam Kasala Viliam Kasala
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: