Andrew Dinn wrote:
I found another glitch in the XTS interop demo which is als a package problem but it was masked by not seeing an exception on the client side. The interop tests creates a JaxWS proxy for the test Participant service which drives XTS and then asks it to run a test. In some cases it passes transaction details using a handler to serialise them into the message. My handler was failing with an NPE but the client proxy did not receive any exception. Is this normal behaviour?
I don't think so, but I'd probably need to see more details / the code to better understand.
The NPE was because the handler failes to create a JaxB context - the call is JAXBContext.newInstance(pkgname); The call throws an exception whose detail message is "Provider com.sun.xml.internal.bind.v2.ContextFactory not found" I assume this is because of a service lookup problem. I'll see if I can work out thow to fix this.
This looks like a problem with dependencies on a JAXB Impl module. Can you check what classloader is set as TCCL / is being used for resolution in JAXBContext.newInstance(..) when that's called by your handler? I guess a dependency on com.sun.xml.bind (with services=import) is missing somewhere.