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?
- CXF versus Java builtins in 1.6 Benson Margulies
- Re: CXF versus Java builtins in 1.6 Alessio Soldano
- Re: CXF versus Java builtins in 1.6 Daniel Kulp
