Richard Wallace wrote:
> Downloading to JDK 5 solved the problem so that must have been it. I
> think I've run into this with another project as well. So annoying that
> Sun insists on throwing everything into the runtime.
>
Yes, in this particular case it caused many problems for developers
(including Sun internal developers, like myself, who worked on the
projects!) who wanted to use the latest JAX-WS/JAXB with JDK 6, things
should be stabilized now with JRE 6 update 4 and i don't anticipate
further incompatible revs of the JAX-WS/JAXB APIs.
BUT i think this is really a modularization issue, we are sort of in an
equivalent of DLL hell for jar files. I would like to specify that
Jersey depends on X, Y, Z with versions and the runtime works out all
the isolation and class loading, then with a maven repo the dependencies
can be downloaded. IIUC OSGi can do the first part... i don't know what
the state of the modularization work in SE 7 is.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109