6 Replies Latest reply on Mar 24, 2009 4:34 AM by Sean Burns

    Trouble getting EJB in ear to work after installing ESB

    Sean Burns Newbie

      Hello,

      I am still trying to get my old apps to work after I have installed JBOSS ESB.

      There seems to be a problem with EJB's in ear's after I have installed ESB.

      Here is a example...

      My JNDIview (from the jmx-console -> JNDIView -> list)


      Global JNDI Namespace
      ...
      +- pocit (class: org.jnp.interfaces.NamingContext)
      | +- TicketRequestEJB (class: org.jnp.interfaces.NamingContext)
      | | +- local (proxy: $Proxy320 implements interface com.pocit.instruction.mobile.authentication.TicketRequest,interface org.jboss.ejb3.JBossProxy)
      ...


      Where pocit is my ear and ticketrequest is my EJB with a local interface,
      now after I install/deploy (even hot deploy of jbossesb.sar does this) ESB into jboss this is what it changes to

      Global JNDI Namespace
      ...
      +- pocit (class: org.jnp.interfaces.NamingContext)
      | +- TicketRequestEJB (class: org.jnp.interfaces.NamingContext)
      | | +- local (proxy: $Proxy320 implements No ClassLoaders found for: com.pocit.instruction.mobile.authentication.TicketRequest (no security manager: RMI class loader disabled))


      It looks like this only affects EJB's in a ear file (because EJB jars directly put into deploy folder still work as normal)


      Please help, this is causing me issues because I get class not found exceptions??

      I tested this with both ESB 4.4 and 4.5 on JBoss 4.2.3.GA

      Sean.