2 Replies Latest reply on Aug 20, 2012 11:31 AM by Martin Thorpe

    JBoss 7 classpath content directory

    Martin Thorpe Newbie

      Hello

       

      Can someone explain why I get these warnings when deploying an application in JBoss?

      All I have is a jar in the WEB-INF/lib directory but it logs warnings referring to the bin/content directory but I am deployed under the standalone dir.

       

      Is there something I have done wrong or omitted to do? I do not want to make this a shared lib or anything it is just packaged within the WAR.

       

       

      17:03:14,020 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-11) Class Path entry jaxb1-impl.jar in "/C:/jboss-7

      .1.1/bin/content/myWar.war/WEB-INF/lib/jaxb-impl-2.2.2.jar"  does not point to a valid jar for a Class-Path refe

      rence.

       

      thanks for reading

        • 1. Re: JBoss 7 classpath content directory
          Stephen Coy Master

          You'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

          1 of 1 people found this helpful
          • 2. Re: JBoss 7 classpath content directory
            Martin Thorpe Newbie

            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