could you test next snapshot ( https://issues.apache.org/jira/browse/TOMEE-953)?
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/5/30 Romain Manni-Bucau <[email protected]> > add -Dopenejb.classloader.forced-load=javax.wsdl > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/5/30 mark.farrell <[email protected]> > >> This worked in Tomcat if a web application includes the Axis 2 >> dependencies >> >> in WEB-INF/lib and makes web service requests itself. >> >> (The application is a client of the web service not implementing the web >> service). >> >> And meant everything required was contained in the web application - no >> changes to Tomcat. >> >> As I started to play with Tomee I decided to front the web service client >> with an EJB, and deploy this seperately from the application, but again >> make >> the distro of the EJB self contained (and simple, hence the war distro) >> and >> allow the implementor to use whatever web service toolkit they want to >> build >> the client. >> >> (The EJB is a client of the web service not implementing the web service, >> i.e. I am not trying to provide a web service frontend to the EJB). >> >> The web application now only uses the very much simplified EJB remote >> interface, and the EJB is the client of the web service. >> >> This worked in the Tomee 1.5.2 release, and it worked in 1.6.0 up to at >> least 17th May. >> >> So, I guess my questions is should this never have worked? And if not, why >> not? And if not, and it never will, where can I learn about what jar files >> should/shouldn't be included where? >> >> Or, (what I'm hoping) is that there is no reason why is shouldn't work and >> will again :-) >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/NoClassDefFoundError-in-1-6-0-SNAPSHOT-class-loader-issue-tp4663348p4663359.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > >
