Spring2 + EJB3 + JBoss405

[cwash5]

So in your web application can you do the following?

SecurityService securityService = (SecurityService)ctx.lookup("java:comp/env/schlange-security/SecurityServiceEjb/local"); 

[dejanp]

This is getting funny. I've put a break point before calling the login() method, and I'm playing with the JNDI bound object:

securityManager instanceof org.schlange.security.server.service.SecurityServi ceEjb
(boolean) false

securityManager instanceof org.schlange.security.server.SecurityService
(boolean) true

So, how can it be instance of SecurityService and not instance of SecurityServiceEjb? There is something really weird in this implementation...

It's a proxy instance. Ejb class is only server side, it can't be accessed client side.

Your problem is, most probably, classloading.

[leetgeezer]

So in your web application can you do the following?

SecurityService securityService = (SecurityService)ctx.lookup("java:comp/env/schlange-security/SecurityServiceEjb/local"); 

I have the same problem and for me the above line works.
Maybe you have a solution?

[Arno Werr]

It might work, but certainly looks ugly.

[tiago182]

It's a proxy instance. Ejb class is only server side, it can't be accessed client side.
Your problem is, most probably, classloading.

If the problem is classloading, how would I solve it? Any idea? Tks

[tiago182]

So in your web application can you do the following?

SecurityService securityService = (SecurityService)ctx.lookup("java:comp/env/schlange-security/SecurityServiceEjb/local"); 

This doesn't work either, I can get another proxy instance looking up for "schlange-security/SecurityServiceEjb/local", which can be casted only to EJBLocalObject.

The global JNDI namespace in my JMX console looks like this:

  +- schlange-security (class: org.jnp.interfaces.NamingContext)
  |   +- SecurityServiceEjb (class: org.jnp.interfaces.NamingContext)
  |   |   +- local (proxy: $Proxy99 implements interface org.schlange.security.server.SecurityService,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
  |   |   +- remote (proxy: $Proxy97 implements interface org.schlange.security.server.SecurityService,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)

[devnulled]

Did you end-up figuring out anything to fix this problem? I'm basically having the exact same issue. I guess I might have to start looking at the JBoss Spring deployment thing, though I'd rather not since this seems like a programming problem which can be fixed somehow.

[tiago182]

Sorry, but at the end I left this aside because I've realised I didn't *really* need such EJB... Just in case, I've just tried it now within JBoss 4.2.2.GA and it still doesn't work: javax.naming.NameNotFoundException. Next time I shall try another application server (if I really need to use EJB3).

[devnulled]

Thanks for the quick reply. I guess I'll keep messing with this... argh...

[dejanp]

Classloading issues with local ejbs are an old, long and sad story. What it boils down to is that you have 2 classloaders for your local interface and you cannot assign instance created in one classloader to a variable in other classloader. (Classes in different classloaders can never be the same class, no matter if they have the same qname or not - that's exactly why we have different classloaders)

Usually there is an option in your app server to turn off the local interface pass-by-ref optimization and use pass-by-value. (Let's ignore the fact that app server is fully aware of all the classloaders it created and could do this on it's own, if needed)