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.1 is needed.
HTH, Glen Wolf, Chris (IT) wrote: > > 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.jar and jaxb-impl.jar and > let the JRE classes > satisfy those dependencies. > > 2.) ...but, then I get the error: "javax.xml.bind.annotation.XmlSeeAlso > cannot be resolved" > even though it appears to be in the runtime: > /opt/1.6.0_04/jre/lib> unzip -t rt.jar | grep XmlSeeAlso > testing: javax/xml/bind/annotation/XmlSeeAlso.class OK > > What do I do? Ignore the JRE JAXB impl and put back all the external > JAXB jars? > > Thanks, > > Chris Wolf > -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. Sender > does not intend to waive confidentiality or privilege. Use of this email > is prohibited when received in error. > > -- View this message in context: http://www.nabble.com/Re%3A-CXF-2.1.1%2C-JAXB%2C-JRE-1.6.0_04-and-codegen-tp18075503p18075987.html Sent from the cxf-user mailing list archive at Nabble.com.
