Spring2 + EJB3 + JBoss405

[tiago182]

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)

Good catch! Would you know how to switch to "pass-by-value" on JBoss 4.x?

[devnulled]

Good catch! Would you know how to switch to "pass-by-value" on JBoss 4.x?

Tiago,

I'm still playing with this issue myself, but I think the answer probably lies in this Wiki entry on JBoss classloading:

http://wiki.jboss.org/wiki/Wiki.jsp?...gConfiguration

Glad I found that to better understand how classloading works in JBoss/EAR's/EJB's, as well as had dejanp reply and send me down that path.. hopefully I'm finally about to get this thing working...

[devnulled]

Changing the ear-deployer.xml file worked for me! I'm going to try and create EJB configs to accomplish the same thing however so I don't have to have this file changed in all of the various dev/qa/prod JBoss env's however.

[tiago182]

Changing the ear-deployer.xml file worked for me! I'm going to try and create EJB configs to accomplish the same thing however so I don't have to have this file changed in all of the various dev/qa/prod JBoss env's however.

Great! I'll follow your path and I'll try this solution as well on the evening after work. Cheers!

[kithalagama]

Hi tiago182,

Let us know if you have found a solution to the prob by changing jboss xml file.

Cheers!
CK