In case it helps others out, I stopped getting the JAXB error when I switched to use Java 1.6.0_05 which includes the 2.1 api. Before, I was using Java 1.6_03 endorsed with JAXB 2.1 api jars. But it turns out the servicemix startup script reset the endorsed directory to '%SERVICEMIX_HOME%\lib\endorsed', so my endorsed jars never got picked up causing the linkage error.
Freeman Fang wrote: > > Hi, > > I just build 3.3 snapshot kit from 3.3 branch, and cxf-wsdl-first > example run successfully for me. > Since the linkage error is usually from version conflict, did you > deploy wsdl-first-cxf-sa-3.3-SNAPSHOT.zip into previouse servicemix > version? > Or could you describe how you deploy the > wsdl-first-cxf-sa-3.3-SNAPSHOT.zip? > > Regards > > Freeman > > -- View this message in context: http://www.nabble.com/JAXB-jars-missing-in-servicemix-3.3-SNAPSHOT--tp15978159p16573757.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
