Calling EJB3 beans over major releases doesn't work.
If we truly ever want something like that then we need to have isolated
class loading bound to JNDI proxies, so that a proxy will use the right
client class versions.
On 10/29/2009 06:54 PM, Dimitris Andreadis wrote:
A user is trying to call ejb3 beans from AS 5.1 -> AS 4.2.3
I believe we do not cover this scenario in our compatibility matrix tests? All we test
Shouldn't we provide "some" ejb3 compatibility guarantees (& testing)
jboss-development mailing list