Glen Mazza-2 wrote: > > Am Mittwoch, den 24.10.2007, 14:54 -0700 schrieb bastien.legras: > > 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. >
I wrote a test class into EJBClient instanciating and returning one of the JAXBean via a static method. I call that test class from the EndPoint implementor. When I call the web service, I can call from App.war the test class of EJBClient.jar which returns a JAXB Bean instance. Glen Mazza-2 wrote: > > Am Mittwoch, den 24.10.2007, 14:54 -0700 schrieb bastien.legras: > > Am Mittwoch, den 24.10.2007, 14:54 -0700 schrieb bastien.legras: > But can the server access those Beans? It has to work with them too, > correct? > Yes, the JAXB beans reside in the AppEJBClient to be instanciable by both the AppWeb and the AppEJB. ... Just to make it very simple : when I move back the JAXB Beans from EJBClient.jar to App.war and redeploy the EAR, everything works again. -- View this message in context: http://www.nabble.com/CXF-%2B-Spring-%3A-Bean-outside-WebApp-have-empty-properties-tf4687334.html#a13396876 Sent from the cxf-user mailing list archive at Nabble.com.
