[
https://issues.apache.org/jira/browse/CXF-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891658#action_12891658
]
Gary Gregory commented on CXF-2907:
-----------------------------------
I do not think the isJaxb21 method ever worked as planned.
When I run against a stock Sun JDK 6 in the debugger I get a build ID of
"hudson-jaxb-ri-2.1-2" for which the method returns false.
If my version of the method is used, true is returned and the test
AegisClientServerTest fails in Maven but passes in Eclipse. Confusing.
It also looks like the method wants a more plain version format like "2.1.2"
Any help is appreciated here.
> 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
> Fix For: 2.2.10
>
> Attachments: 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].
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
