CXF
  1. CXF
  2. CXF-2907

Allow DynamicClientFactory to use any JAXB version 2.1 or greater

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.9
    • Fix Version/s: 2.2.10
    • Component/s: JAXB Databinding
    • Labels:
      None

      Description

      I want to use JAXB 2.2.1 to benefit from a JAXB bug fix but I am having problems getting CXF to recognize it is there.

      All is well when we use JAXB 2.1.13.

      I followed the instructions here to use JAXB on top of Java 6: https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

      I think the problem is the way CXF detects the JAXB version in DynamicClientFactory#isJaxb21(SchemaCompiler).

      The implementation fails to see JAXB 2.2.1 because the build id is not in the expected format: hudson-jaxb-ri-2.2-7

      Has anyone else run into this issue? I am using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug CXF-2900.

      My details:

      Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
      Java version: 1.6.0_20
      Java home: C:\Program Files\Java\jdk1.6.0_20\jre
      Default locale: en_US, platform encoding: Cp1252
      OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

      1. CXF-2907.diff
        2 kB
        ggregory@seagullsw.com
      2. cxf-systests-databinding-pom.diff
        19 kB
        ggregory@seagullsw.com
      3. DynamicClientFactoryTest.diff
        5 kB
        ggregory@seagullsw.com

        Activity

        ggregory@seagullsw.com created issue -
        ggregory@seagullsw.com made changes -
        Field Original Value New Value
        Attachment DynamicClientFactoryTest.diff [ 12450284 ]
        ggregory@seagullsw.com made changes -
        Description I want to use JAXB 2.2.1 to benefit from a JAXB bug fix but I am having problems getting CXF to recognize it is there.

        All is well when we use JAXB 2.1.13.

        I followed the instructions here to use JAXB on top of Java 6: https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

        I think the problem is the way CXF detects the JAXB version in DynamicClientFactory#isJaxb21(SchemaCompiler).

        The implementation fails to see JAXB 2.2.1. The implementation looks odd to me, but, hey, that's me :)

        Has anyone else run into this issue? I am using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug [CXF-2900].
        I want to use JAXB 2.2.1 to benefit from a JAXB bug fix but I am having problems getting CXF to recognize it is there.

        All is well when we use JAXB 2.1.13.

        I followed the instructions here to use JAXB on top of Java 6: https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

        I think the problem is the way CXF detects the JAXB version in DynamicClientFactory#isJaxb21(SchemaCompiler).

        The implementation fails to see JAXB 2.2.1 because the build id is not in the expected format: hudson-jaxb-ri-2.2-7

        Has anyone else run into this issue? I am using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug [CXF-2900].
        ggregory@seagullsw.com made changes -
        Attachment DynamicClientFactoryTest.diff [ 12450284 ]
        ggregory@seagullsw.com made changes -
        Attachment DynamicClientFactoryTest.diff [ 12450321 ]
        ggregory@seagullsw.com made changes -
        Description I want to use JAXB 2.2.1 to benefit from a JAXB bug fix but I am having problems getting CXF to recognize it is there.

        All is well when we use JAXB 2.1.13.

        I followed the instructions here to use JAXB on top of Java 6: https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

        I think the problem is the way CXF detects the JAXB version in DynamicClientFactory#isJaxb21(SchemaCompiler).

        The implementation fails to see JAXB 2.2.1 because the build id is not in the expected format: hudson-jaxb-ri-2.2-7

        Has anyone else run into this issue? I am using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug [CXF-2900].
        I want to use JAXB 2.2.1 to benefit from a JAXB bug fix but I am having problems getting CXF to recognize it is there.

        All is well when we use JAXB 2.1.13.

        I followed the instructions here to use JAXB on top of Java 6: https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

        I think the problem is the way CXF detects the JAXB version in DynamicClientFactory#isJaxb21(SchemaCompiler).

        The implementation fails to see JAXB 2.2.1 because the build id is not in the expected format: hudson-jaxb-ri-2.2-7

        Has anyone else run into this issue? I am using a CXF 2.2.10 snapshot build to work around CXF 2.2.9 bug [CXF-2900].

        My details:

        Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
        Java version: 1.6.0_20
        Java home: C:\Program Files\Java\jdk1.6.0_20\jre
        Default locale: en_US, platform encoding: Cp1252
        OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

        ggregory@seagullsw.com made changes -
        Attachment CXF-2907.diff [ 12450351 ]
        Daniel Kulp made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Daniel Kulp [ dkulp ]
        ggregory@seagullsw.com made changes -
        Attachment cxf-systests-databinding-pom.diff [ 12450382 ]
        Daniel Kulp made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Mark Thomas made changes -
        Workflow jira [ 12516395 ] Default workflow, editable Closed status [ 12604969 ]
        Mark Thomas made changes -
        Reporter Gary Gregory [ ggregory@seagullsw.com ] Gary D. Gregory [ garydgregory ]

          People

          • Assignee:
            Daniel Kulp
            Reporter:
            Gary Gregory
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development