Dimitris Andreadis wrote:
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
uniform it should be easy to make it work without isolated classloading.
I disagree. There was large discussion in the past on this topic, and
the consensus was that the community releases would favor delivering
innovation rapidly over ensuring backwards compatibility. True wire
compatibility between major revs is a non-trivial engineering effort.
Jason T. Greene
JBoss, a division of Red Hat