Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-1187

FP01 rpm testing problems with hibernate validator jar

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 4.3.0.GA_CP02_FP01
    • 4.3.0.GA_CP02_FP01
    • Build, Seam
    • None

      I finally was able to get everything setup and tested the FP01 rpms on a rhel 5 machine. I have successfully installed the jbossas and jboss-seam2 packages and dependencies. I was able to start the jbossas server.

      I have attempted to deploy the booking example and I am getting the following exception during deployment.

      Caused by: java.lang.NoClassDefFoundError: org/hibernate/validator/ClassValidator
      at java.lang.Class.getDeclaredMethods0(Native Method)
      at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
      at java.lang.Class.privateGetPublicMethods(Class.java:2519)
      at java.lang.Class.getMethods(Class.java:1406)
      at org.jboss.seam.Component.hasAnnotation(Component.java:1070)
      at org.jboss.seam.Component.<init>(Component.java:229)

      It looks like the hibernate validator jar is not there. The jar is linked in the production server as below:

      hibernate-validator.jar -> /usr/share/java/hibernate3-validator.jar

      but the target jar does not exist. The " hibernate3-validator-3.0.0-0jpp.ep1.3.el5:0.noarch" package is part of the FP channel but is not on my system. There must be some missing dependency setting or something.

      This effectively block my testing - so I will continue once there are fresh RPMs on stage - I'm assuming productization and release eng can take a look at this. Let me know when it is ready. Please smoke test the RPMs (at least one example) prior to qa handover.

              permaine Permaine Cheung
              jbalunas@redhat.com Jay Balunas
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: