1 Reply Latest reply on Dec 6, 2004 9:30 AM by Bernd Zeitler

    Classloading Issue

    Florian Rosenberg Newbie

      Hi,

      i have my EJB and a WebService for my session bean on JBoss 3.2.6.
      I pack the WSR and the JAR in an EAR. Furthermore I need some custom classloading (Isolation with Overriding). My "custom jars" are packed togehter with my classes in the JAR file of the EJB. I'm not sure if this is the right location (I images they should be in the root of the EAR???)

      I have a jboss-app.xml where I specify the following:

      <jboss-app>
       <loader-repository>
       net.ponifaax.swa:loader=GooAmazon
       <loader-repository-config>
       java2ParentDelegation=false
       </loader-repository-config>
       </loader-repository>
      </jboss-app>
      


      The "net.ponifaax.swa" denotes my package name, the GooAmazon my EAR file name. Is this correct, or what else should I specify here, I'm not sure, the docs didn't make it clear to me.

      When i deploy my ear i get the following error:

      20:51:15,153 INFO [EjbModule] Deploying GooAmazon
      20:51:15,874 INFO [EJBDeployer] Deployed: file:/C:/jboss-3.2.6/server/all/tmp/deploy/tmp36215GooAmazon.ear-contents/GooAmazonEJB.jar
      20:51:16,134 ERROR [MainDeployer] could not start deployment: file:/C:/jboss-3.2.6/server/all/tmp/deploy/tmp36215GooAmazon.ear-contents/GooAmazonEJB.w
      sr
      java.lang.ExceptionInInitializerError
       at org.apache.axis.deployment.wsdd.WSDDDeployment.deployMapping(WSDDDeployment.java:398)
       at org.apache.axis.deployment.wsdd.WSDDDeployment.getTypeMappingRegistry(WSDDDeployment.java:572)
       at org.jboss.net.axis.Deployment.getTypeMappingRegistry(Deployment.java:335)
       at org.jboss.net.axis.Deployment.installTypeMappingWithOptions(Deployment.java:348)
       at org.jboss.net.axis.Deployment.getTypeMappingRegistry(Deployment.java:330)
       at org.jboss.net.axis.Deployment.deployToRegistry(Deployment.java:311)
       at org.jboss.net.axis.server.AxisService.startAxisDeployment(AxisService.java:210)
       at org.jboss.net.axis.server.AxisService.start(AxisService.java:545)
       at org.jboss.net.axis.server.AxisService.start(AxisService.java:514)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:821)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
       at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
      [.......truncated......]
      



      Any ideas?
      greets florian


        • 1. Re: Classloading Issue
          Bernd Zeitler Expert

          The jboss-app.xml looks ok.
          Just guessing:
          probably you are doing some initialisation in the EJBs constructor. This initialisation needs something not yet deployed (well, whatever ;-). You must not do this. Use the ejbCreate for doing the initialisation.

          If this doesn't help just provide some more information.