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

Upgrade to jackson 2.10 (if possible)

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Do
    • Critical
    • fuse-7.8-GA
    • None
    • None
    • None

    Description

      FUSEQE-9077 mentions problems that some Fuse 7 BOMs use Validation API 1 and some - Validation API 2 (Hibernate Validator 5 and Hibernate Validator 6 respectively).

      https://issues.apache.org/jira/browse/CXF-8151 Upgrades to Validation API 2 in CXF 3.4.0 and it potentially could be backported to "our" CXF in jboss-fuse/cxf fork.

      I tried this, but:

      • swagger2 (1.5.17) still has OSGi import range for Validation API 1 - but I've fixed this in our fork in https://github.com/jboss-fuse/swagger-core/commits/v1.5.24-fuse-77x
      • CXF-8151 also updates swagger3 (2.1.x) to match Validation API 2, but at the same time, this swagger3 2.1.x starts OSGi importing Jackson 2.10+
      • I tried downgrading swagger3 to 2.0.x (yes - swagger versioning is ugly), but this brought back requirement on Validation API 1

      So in theory, CXF could switch to jackson 2.10+ (some Camel components use this version anyway), but Fuse 7 BOMs provide jackson 2.8 and 2.9 (depending on flavor).

      This is PM level decision about jackson, especially because recently we've switched to whitelist-enabled jackson 2.8/2.9.

      janstey@redhat.com, gmalinko, jonnychristison, yfang@redhat.com, acosenti FYI ^^^.

      Attachments

        Issue Links

          Activity

            People

              ggrzybek Grzegorz Grzybek
              ggrzybek Grzegorz Grzybek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: