cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CXF-2907) Allow DynamicClientFactory to use any JAXB version 2.1 or greater
Date Sat, 24 Jul 2010 03:45:51 GMT

    [ https://issues.apache.org/jira/browse/CXF-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891918#action_12891918
] 

Gary Gregory edited comment on CXF-2907 at 7/23/10 11:45 PM:
-------------------------------------------------------------

The problem is that the Maven build runs the test with the JRE version of Xerces, which is
very old.

The tests I run from Eclipse are set up with Xerces 2.9.1, presumably as configured by the
Maven Eclipse plugin.

When I add Xerces 2.9.1 to the {{cxf-systests-databinding}} POM (2.10.0 is not in the M2 repo
yet), the project {{cxf-systests-databinding}} passes all tests.

Now, the real issue is that Xerces is not shipped with CXF eventhough Xalan is. I am sure
there is a reason for that but shipping the current version of Xalan (2.7.1) and not the version
of Xerces (2.9.0) that Xalan ships with seems like asking for trouble.

So this ticket should add Xerces 2.9.1 (and then 2.10.0 when it is in the M2 repo) to this
POM.

Another ticket should add Xerces to the distro IMO.

Thoughts?

      was (Author: ggregory@seagullsw.com):
    The problem is that the Maven build runs the test with the JRE version of Xerces, which
is very old.

The tests I run from Eclipse are set up with Xerces 2.9.1, presumably as configured by the
Maven Eclipse plugin.

When I add Xerces 2.9.1 to the {{cxf-systests-databinding}} POM (2.10.0 in not in the M2 repo
yet), the project {{cxf-systests-databinding}} passes all tests.

Now, the real issue is that Xerces is not shipped with CXF eventhough Xalan is. I am sure
there is a reason for that but shipping the current version of Xalan (2.7.1) and not the version
of Xerces (2.9.0) that Xalan ships with seems like asking for trouble.

So this ticket should add Xerces 2.9.1 (and then 2.10.0 when it is in the M2 repo) to this
POM.

Another ticket should add Xerces to the distro IMO.

Thoughts?
  
> Allow DynamicClientFactory to use any JAXB version 2.1 or greater
> -----------------------------------------------------------------
>
>                 Key: CXF-2907
>                 URL: https://issues.apache.org/jira/browse/CXF-2907
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAXB Databinding
>    Affects Versions: 2.2.9
>            Reporter: Gary Gregory
>            Assignee: Daniel Kulp
>             Fix For: 2.2.10
>
>         Attachments: CXF-2907.diff, cxf-systests-databinding-pom.diff, DynamicClientFactoryTest.diff
>
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message