Am Mittwoch, den 24.10.2007, 14:54 -0700 schrieb bastien.legras: > Hello, > > First of all, my application is an EAR having 3 modules : > - App.war > - AppEJBClient.jar > - AppEJB.jar > > App.war has several CXF Web Services working fine. > > Problems appear when I move my Beans (generated by WSDL2Java) from App.war > to AppEJBClient.jar. > > Each time I call the Web Services I get Beans with null properties. >
Can you forget about the web service for the moment, and just try to initialize/instantiate some of the JAXB beans within the AppEJBClient code? I would like to see if we can separate web service issues vs. classloader issues. > AppEJBClient.jar is referenced in the App.war's MANIFEST, so I can't think > my issue has anything to do with class visibility as other Classes from > AppEJBClient.jar are well instanciated from App.war. > But can the server access those Beans? It has to work with them too, correct? HTH, Glen > Finally, I don't get any Exception logged by the CXF framework. I'm using > CXF 2.0.2. > > Thanks for your help. > > Regards, > > Bastien LEGRAS
