0 Replies Latest reply on Nov 25, 2002 7:40 PM by deas

    JBoss 3.0.4: Deployment classloading problem

    deas

      Hallo everybody,

      even though I'm sure that the following should qualify as a FAQ, I cannot find the answer anywhere.

      My .ear was working fine with JBoss 3.0.0 / Tomcat 4.0.3, but it fails after upgrading to JBoss 3.0.4 / tomcat 4.1.12, yielding:

      2002-11-25 22:31:44,811 ERROR [org.jboss.ejb.EJBDeployer] Verfiy failed
      java.lang.NoClassDefFoundError: org/apache/ojb/broker/PersistenceBrokerException
      at java.lang.Class.getDeclaredMethods0(Native Method)
      at java.lang.Class.privateGetDeclaredMethods(Class.java:1627)

      This class (OJB) is not in the .ear, as it is already used
      by the OJB MBean:

      2002-11-25 23:55:02,793 INFO [STDOUT] ** OJB-ODMG MBean integration
      2002-11-25 23:55:02,794 INFO [STDOUT] ** ODMGFactory: org.jboss.ojb.odmg.ODMGFactory / DefaultDomain:
      service=ODMG,name=ojb/defaultODMG
      2002-11-25 23:55:02,795 INFO [STDOUT] ** Use ODMGFactory via lookup:
      2002-11-25 23:55:02,795 INFO [STDOUT] ** ODMGFactory factory = (ODMGFactory) ctx.lookup(java:/ojb/def
      aultODMG)
      2002-11-25 23:55:02,795 INFO [STDOUT] ** Implementation odmg = factory.getInstance();
      2002-11-25 23:55:02,795 INFO [org.jboss.ojb.odmg.ODMGFactory] Started
      2002-11-25 23:55:02,796 INFO [org.jboss.ojb.pb.PBFactory] Starting
      2002-11-25 23:55:02,832 INFO [org.jboss.ojb.pb.PBFactory] PBFactory: org.jboss.ojb.pb.PBFactory / Def
      aultDomain:service=PB,name=ojb/PBAPI
      2002-11-25 23:55:02,833 INFO [org.jboss.ojb.pb.PBFactory] Lookup PBFactory via 'java:/ojb/PBAPI'
      2002-11-25 23:55:02,834 INFO [org.jboss.ojb.pb.PBFactory] Started
      2002-11-25 23:55:02,835 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/opt/jboss-3.
      0.4_tomcat-4.1.12/server/devel/deploy/ojb-service.xml

      Hence, I would prefer if that one could be used.

      The corresponding jars are in lib/ext, and the classpath is set accordingly in conf/jboss-service.xml.

      How can I make this common "shared" jar available to the deployment unit in jboss 3.0.4 ?

      regards
      Andreas