aspose file tools*
The moose likes Web Services and the fly likes Novel solution to a common problem: getting past the JAXB 2.0/2.1 API mismatch Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "Novel solution to a common problem: getting past the JAXB 2.0/2.1 API mismatch " Watch "Novel solution to a common problem: getting past the JAXB 2.0/2.1 API mismatch " New topic
Author

Novel solution to a common problem: getting past the JAXB 2.0/2.1 API mismatch

Stuart Rogers
Ranch Hand

Joined: Oct 02, 2008
Posts: 139
Seasons Greetings all,

Recently I had to add integration testing to some functioning code but kept running
into the dreaded "JAXB 2.0 API is being loaded from the bootstrap loader...
...needs 2.1 API. Use the endorsed directory mechanism..." error. I couldn't use the
standard 'put files in the endorsed directory' solution as I don't have access to the
the production server where this code will eventually live. For the same reason I can't
update the base Java to some other, newer version. As the production code ran fine I figured
this could be fixed by placing the correct collection of artifacts in the pom.

This is what worked for me. YMMV.



Hope this saves some people some hassle.

Merry Christmas!


Still-learning Steve
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Novel solution to a common problem: getting past the JAXB 2.0/2.1 API mismatch