3 Replies Latest reply on Aug 3, 2011 9:49 AM by jesper.pedersen

    Validator problems

    mphillip

      Hi guys,

       

      I've been having a go at running the validator using the standalone ironjackamar and have run into a bit of a problem (on both windows and linux).

       

      Firstly, the JEE classes are not in the classpath for the validator:

       

      C:\jboss.ironjackamar\ironjacamar-1.0.0.Final\doc\validator>java -classpath ..\..\lib\ironjacamar-validator-cli.jar;..\.

      .\lib\ironjacamar-common-spi.jar;..\..\lib\jboss-logging.jar;..\..\lib\jboss-common-core.jar;..\..\lib\ironjacamar-spec-

      api.jar;..\..\lib\papaki-core.jar;..\..\lib\javassist.jar;..\..\lib\ironjacamar-common-impl.jar;..\..\lib\ironjacamar-co

      mmon-impl-papaki.jar;..\..\lib\ironjacamar-common-api.jar;..\..\lib\ironjacamar-validator.jar org.jboss.jca.validator.cl

      i.Main c:\test\MQRA\7.0.1-noclasspath\wmq.jmsra.rar

      Exception in thread "main" java.lang.NoClassDefFoundError: javax/jms/JMSException

              at java.lang.Class.forName0(Native Method)

              at java.lang.Class.forName(Class.java:247)

              at org.jboss.jca.validator.Validation.createResourceAdapter(Validation.java:256)

              at org.jboss.jca.validator.Validation.validate(Validation.java:155)

              at org.jboss.jca.validator.cli.Main.main(Main.java:92)

      Caused by: java.lang.ClassNotFoundException: javax.jms.JMSException

              at java.net.URLClassLoader$1.run(URLClassLoader.java:202)

              at java.security.AccessController.doPrivileged(Native Method)

              at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

              at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

              at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

              ... 5 more

       

       

      I added them in using the JEE jar I used to create the RA and then ran into the following exception:

       

       

      C:\jboss.ironjackamar\ironjacamar-1.0.0.Final\doc\validator>java -classpath ..\..\lib\ironjacamar-validator-cli.jar;..\.

      .\lib\ironjacamar-common-spi.jar;..\..\lib\jboss-logging.jar;..\..\lib\jboss-common-core.jar;..\..\lib\ironjacamar-spec-

      api.jar;..\..\lib\papaki-core.jar;..\..\lib\javassist.jar;..\..\lib\ironjacamar-common-impl.jar;..\..\lib\ironjacamar-co

      mmon-impl-papaki.jar;..\..\lib\ironjacamar-common-api.jar;..\..\lib\ironjacamar-validator.jar;C:\k000\src\com.ibm.mq.con

      nector\src\3rdparty\j2ee.jar org.jboss.jca.validator.cli.Main c:\test\MQRA\7.0.1-noclasspath\wmq.jmsra.rar

      java.io.IOException: . can't be created

              at org.jboss.jca.validator.Validation.validate(Validation.java:171)

              at org.jboss.jca.validator.cli.Main.main(Main.java:92)

      Validation unknown

       

       

      On linux I was running as root, so there should be no file permission issues.

       

      Any thoughts?

        • 1. Re: Validator problems
          jesper.pedersen

          Yes, IronJacamar/Standalone doesn't ship the entire EE API, so you will need to add the JMS API yourself.

           

          Hmm, by default it should output in the current working directory. Try adding "-output report" to the command line and see if that changes anything.

          • 2. Re: Validator problems
            mphillip

            Woo-hoo - that did the trick!

             

            C:\jboss.ironjackamar\ironjacamar-1.0.0.Final\doc\validator>java -classpath ..\..\lib\ironjacamar-validator-cli.jar;..\..\lib\ironjacamar-common-spi.jar;..\..\lib\jboss-logging.jar;..\..\lib\jboss-common-core.jar;..\..\lib\ironjacamar-spec-api.jar;..\..\lib\papaki-core.jar;..\..\lib\javassist.jar;..\..\lib\ironjacamar-common-impl.jar;..\..\lib\ironjacamar-common-impl-papaki.jar;..\..\lib\ironjacamar-common-api.jar;..\..\lib\ironjacamar-validator.jar;C:\k000\src\com.ibm.mq.connector\src\3rdparty\j2ee.jar org.jboss.jca.validator.cli.Main -output report c:\test\MQRA\7.0.1\wmq.jmsra.rar

            Validation sucessful

             

            Thank you!

            • 3. Re: Validator problems
              jesper.pedersen

              Ok, my latest commit should fix this problem - that was the next step to try