[
https://issues.apache.org/jira/browse/CXF-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bastien LEGRAS resolved CXF-1135.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0-RC
2.0.1
This issue is pure configuration dependend, below my resolution procedure :
bastien.legras wrote:
> After hours of bloody debugging /tracing through CXF code, I found the root
> cause of my issue :
>
> It has to do with my JBOSS 4.0.4 GA environment I forgot to mention :(
>
> For the one who care, I wrote below a detailed explanation + solution
>
> Detailed Explanation :
> JAXBContext is already "classloaded" via jboss-j2ee.jar
> (/server/default/lib) prior the one packaged with CXF (jaxb-api-2.0.jar).
> Jboss's JABXBContext works fine for CXF as long as your JAX Beans are
> packaged inside the web services application. But once you move your JAX
> Beans outside the application, things changes in the JAXBEncoderDecoder :
>
> line 388 (for CXF 2.0.2) :
> obj = unmarshalWithClass ? u.unmarshal((XMLStreamReader)source, clazz) : u
>
> return an object with null properties as the Unmarshaller is not the right
> one as its implementor comes from Jboss instead of CXF.
>
>
> Solution :
> To fix the issue I found no other solution than copying the following jars
> to JBOSS_HOME/lib/endorsed directory (server/default/lib is not enough) :
> jaxb-api-2.0.jar
> jaxb-impl-2.0.5.jar
> geronimo-activation_1.1_spec-1.0-M1.jar
> stax-api-1.0.1.jar
>
>
> Hope this will help others !
>
> Cheers,
>
> Bastien LEGRAS
> JAXB Context failure when beans are packaged outside application
> ----------------------------------------------------------------
>
> Key: CXF-1135
> URL: https://issues.apache.org/jira/browse/CXF-1135
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Resources
> Affects Versions: 2.0, 2.0.2
> Environment: Java 1.5 / Eclipse 3.3 / JBOSS 4.0.4 / WINXP 32bits
> Reporter: Bastien LEGRAS
> Fix For: 2.0.1, 2.0-RC
>
>
> When Beans (generated through WSDL2Java) are moved to a external jar (added
> to the web application classpath), the Spring implementors instanciate Beans
> with null properties. Bringing back the beans within the web application
> solves immediately.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
