Carlo de Wolf wrote:
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.
It is never going to work if you don't plan for it. Customers will ask for this, and
many will expect this to work, so prepare a workaround for 4<->5 and put it in your
for 5<->6 :-)
I mean it might be hard to do it between 4 and 5, but between 5 & 6 where the codebase
uniform it should be easy to make it work without isolated classloading.
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 is
> ejb2 access.
> Shouldn't we provide "some" ejb3 compatibility guarantees (&
> going forward?
> jboss-development mailing list