Thanks again, I'd like to use these versions as we're already using them elsewhere. Why would they need to be compatible with JAXB 2.0?
We are using these same jars in other places without incident.
-----Original Message-----
From: Tatu Saloranta [mailto:tsaloranta_at_gmail.com]
Sent: Tuesday, December 08, 2009 12:20 AM
To: dev_at_jaxb.dev.java.net
Subject: Re: NoClassDefFoundError on JAXBException
On Mon, Dec 7, 2009 at 8:56 PM, Josh Hester <Josh.Hester_at_sas.com> wrote:
> Thank you Tatu!
>
> I should have mentioned that I'm including the following jars:
>
> <classpathentry kind="lib" path="jaxb1-impl.jar"/>
> <classpathentry kind="lib" path="activation.jar"/>
> <classpathentry kind="lib" path="jsr173_1.0_api.jar"/>
> <classpathentry kind="lib" path="jaxb-xjc.jar"/>
> <classpathentry kind="lib" path="jaxb-impl.jar"/>
> <classpathentry kind="lib" path="jaxb-api.jar"/>
>
> Any other ideas?
I could be wrong, but maybe those are JAXB v1.0 jars? (which are not
compatible with JAXB v2.0)
So it could be version incompatibility issue.
This seems likely, given that implementation jar specifically
indicates its version 1.0.
And unless you really do want to use ancient (and for all purposes
obsolete) version 1.0, you want to upgrade to 2.0.
Hope this helps,
-+ Tatu +-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: dev-help_at_jaxb.dev.java.net