Geek asks and answers

How compatible are backward compatible EJB containers?

I inherited an application running on JBoss 2.4.3 (which, in my opinion, is compatible with EJB spec 2.0), and I have quite a few problems (for example, the ability to use the modern log4j "Logger" apis [JBoss 2.4 specific problems that push me to update]).

I understand that I can use the EJB 2.1 container (Jboss 4) without problems, but should I expect further progress?

What are the backward compatibility requirements for EJB?

Are they designed for backward compatibility through major versions?

Are application developers provided fully backward compatible?

What changes are needed to keep the old application consistent? (configuration or recompilation small or large?) etc.

+1
source share
3 answers

log4j and EJB 2.0 are not related. If you have problems with log4j, then most likely this is a problem with the class, and not a problem with EJB 2.0 support. Your old application probably suggests that log4j is somewhere on the way to the system class.

+1
source

http://what-when-how.com/enterprise-javabeans-3/backward-compatibility-and-interoperability-with-ejb-2/ states that

The EJB 3 specification requires that all supporting containers support EJB 2

This is a good sign. Next, we talk about mixing the functionality of EJB 2 and 3. Therefore, there may be some exceptions, but in fact it should not be almost impossible somewhere.

; , jboss.

+1

EJB:

enter image description here

+1
source

More articles:


All Articles