jaxb-2.1.6 or higher.
Thanks,
-Chris W.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2008 3:14 PM
To: users@cxf.apache.org
Subject: Re: CXF-2.1.1, JAXB, JRE-1.6.0_04 and codegen
Glen,
JDK 1.6.0_04 now include JAXB 2.1.3 instead of the 2.
Glen,
JDK 1.6.0_04 now include JAXB 2.1.3 instead of the 2.0 versions used
in the older versions of the JDK. Thus, it shouldn't be necessary,
even for Metro.
That said, we ship 2.1.6 (and I just noticed 2.1.7 is out) which
includes some performances fixes that you may want anyway. Th
I think so, but this might be more of a Dan Kulp question. As best I know,
if you use Metro, they want you to put the 2.1 JAXB jars in the endorsed
directory of the SDK because the default JAXB in the JRE is 2.0, and Metro
can't work with those. It *may* be the same story with CXF, i.e., JAXB 2.
Just switched up to CXF-2.1.1 from 2.0. I see that JAXB in now
available
in JDK-1.6.0_04, so I remove external JAXB jars, however, I then get
two problems:
1.) wsdl2java won't run. To fix this, I need to put back the external
JAXB jar, "jaxb-xjc.jar",
however, I can still leave out jaxb-api
