-
1. Re: JBoss 7 classpath content directory
sfcoy Aug 20, 2012 11:23 AM (in response to martsecurit)1 of 1 people found this helpfulYou're asking for trouble deploying JAXB implementations in your webapp. As JBoss AS 7.1.x ships with a version of JAXB 2.2 it would be a good idea to remove this from your application. JBoss needs to perform some HPFM* in order to get it's implementation to override the one in your JDK. Leaving your version in place may cause strange and not so wonderful behaviour.
As far as the actual warning is concerned, that is just reporting that the jar jaxb-impl-2.2.2.jar contains a manifest classpath entry referencing a jar named "jaxb1-impl.jar", which it cannot see in your application.
* Hocus Pocus F... Magic
-
2. Re: JBoss 7 classpath content directory
martsecurit Aug 20, 2012 11:31 AM (in response to sfcoy)Hello
Just for your info I need to include this Sun JAXB implementation for correct replacement of namespaces which does not work with the core supplied classes.
It is no problem and runs well under JBoss and Websphere you just need to make sure you have the package-info correct and then it works fine.
Thanks for the reply