Apparently you can, but the only workaround I have been able to find is to download and install the JAXB 2.1 API and RI jars in the lib/endorsed dirs as mentioned here: http://weblogs.java.net/blog/kohsuke/archive/2006/12/jaxb_21_release.html
There is a mention of a fix implemented in JAXB recently in these two blog entries (not sure which JAXB release), but based on the classloader trick he apparently uses I think this will break in OSGi. http://weblogs.java.net/blog/kohsuke/archive/2007/02/running_jaxbws.html http://weblogs.java.net/blog/kohsuke/archive/2007/02/howitworks_runn.html Thanks, Chris On Dec 19, 2007 12:07 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > Does this mean we can't compile trunk on JDK 1.6 ? > > On Dec 19, 2007 3:19 AM, Freeman Fang <[EMAIL PROTECTED]> wrote: > > > Hi Chris, > > To fix SM-1168, we need a fix in cxf, both cxf 2.0.4 snapshot and cxf > > 2.1 snapshot include this fix > > For servicemix 3.2.2 snapshot, we use cxf 2.0.4 snapshot, which is > > still based on jaxws2.0 and jaxb 2.0, so you have no jdk1.6 issue. And > > for servicemix 3.2.x release we can get a stable cxf 2.0.4 version which > > is not changed so much but have update we need. > > > > But for servicemix 3.3 snapshot, I think we should support jaxws2.1 and > > jaxb 2.1 for long term run, so I introduce cxf 2.1 snapshot here. > > > > Thanks for your patch and I will apply it soon > > > > Best Regards > > > > Freeman > > > > Chris Custine wrote: > > > Following up, I just realized that you did apply this to 3.2 and it > did > > not > > > require CXF 2.1 from the looks of it. > > > > > > I found the cause for the compile failure in trunk and created a Jira > > with > > > the fix here: https://issues.apache.org/activemq/browse/SM-1181 > > > > > > Thanks, > > > Chris > > > > > > On Dec 18, 2007 4:56 PM, Chris Custine <[EMAIL PROTECTED]> wrote: > > > > > > > > >> I noticed that Freeman's fix for SM-1168< > > https://issues.apache.org/activemq/browse/SM-1168>included an upgrade to > > CXF > > >> 2.1 SNAPSHOT and I was wondering if that was intentional and part of > > the > > >> fix for the issue, or if it was not related to SM-1168? CXF > > 2.1apparently has a dependency on JAXB > > >> 2.1 which I am pretty sure is going to cause problems if compiling > > under > > >> JDK 1.6 since 1.6 already includes JAXB 2.0 (there are workarounds, > but > > >> they require manual installation of endorsed JAXB 2.1 jars). > > >> > > >> In addition, downgrading to JDK 1.5 to build seems to have some > issues > > >> while building wsdl-first-jsr181-su (and maybe others) because some > of > > the > > >> xfire tooling has specified JAXB 2.0 API and the build fails at that > > >> point. > > >> > > >> I was hoping Freeman can give a little info on the move to CXF > > 2.1snapshot and if there is any way way we can implement this fix for > > SM-1168 > > >> without it since we probably need to fix this issue for 3.2 as well > and > > I > > >> think upgrading to CXF 2.1 might be too much for a bug fix branch. > > >> > > >> Thanks, > > >> Chris > > >> > > >> > > > > > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
