The reason they need to be in the same classloader is CXF keeps a map of destinations. In separate war files, the services would be in separate classloaders. To accomplish what you want, the CXF jar, its dependencies, if you are using object binding then the object jar too, all need to be in the tomcat common classloader (e.g. tomcat's lib directory, not in a war), which is generally a bad idea unless its absolutely necessary. If you aren't using object binding, the extra complexity introduced doesn't really buy you much over just doing a localhost route of HTTP, since you are still paying the serialization time.
________________________________________ From: jaybytez [[email protected]] Sent: Tuesday, June 21, 2011 4:23 PM To: [email protected] Subject: Re: Local Transport Benchmarks Asking a quick beginner question about this. The Coloc information as well as this post says: /They MUST be in the same classloader. This would be normal if on the same Bus./ So in order for the local to work with sharing classloader and bus, the client and server would essentially need to be in the same war file? Is that the case? What if I have a war file making a call to another war file in the same application server, could I take advantage of using the local? Thanks...jay -- View this message in context: http://cxf.547215.n5.nabble.com/Local-Transport-Benchmarks-tp3398693p4512336.html Sent from the cxf-user mailing list archive at Nabble.com.
