Millies, Sebastian wrote:
indeed removing %TUSCANY_HOME%\lib from the client's classpath works
around the problem.
I've done a simple text search for "JAXBContext" on the source code.
The class org.apache.tuscany.sca.databinding.jaxb.JAXBContextCache
creates JAXBContexts and uses classloaders, so maybe if the
application classloader does not have the built-in versions
first, something goes wrong there.
Tuscany isn't running on the client side, so I don't think this is where
the client's JAXBContext is being created. I'm trying to create a test
case to reproduce the problem myself so that I can investigate further.
Simon
-- Sebastian
From: Simon Nash [mailto:[email protected]]
Sent: Wednesday, September 08, 2010 12:16 PM
To: [email protected]
Subject: Re: FW: JAXB 2.1 incompatibilty between Tuscany 1.6 and JDK
1.6.0_18
[snip]
What's puzzling me is that both JAX-WS and JAXB are part of the
JDK and I would have expected the built-in versions to be picked up
by the client code in preference to anything on the classpath.
There must be some code somewhere that's creating a JAXBContext by
looking on the classpath. I'll try to figure out where the
JAXBContext is getting created.
Simon
[snip]
