On Thursday 16 September 2010 11:22:56 am Benson Margulies wrote: > We've got some code that works fine with a JAX-WS client via wsdl2java > materials when run in isolation. Dropped into open office (don't ask), we > end up with an error and a non-CXF backtrace. Another JAR of ours included > in the classpath works fine. What possible pranks could OO be playing to > prevent CXF from setting up shop?
The only thing I can really think of is if they already have some ancient versions of some of our 3rd party jars on their classpath which is causing issues with us. Or maybe one of our jars is newer and is being placed BEFORE theirs and that's causing some issues in things OO is trying to do. Good luck. :-) -- Daniel Kulp [email protected] http://dankulp.com/blog
