EJB specifications and Java versions - backwards compatibility?

You shouldn't even have to "upgrade" the Java code, since I think older code can only be incompatible at source level due to identifiers that collide with newly introduced keywords, but that's not a problem at the bytecode level.

You shouldn't even have to "upgrade" the Java code, since I think older code can only be incompatible at source level due to identifiers that collide with newly introduced keywords, but that's not a problem at the bytecode level. So your old Java 1.3/EJB 2.0 EARs should still run unchanged on a Java 5/EJB 3 appserver, and you could even do bugfixes in code and compile it with -target 1.3 on a modern JDK without having to fix the colliding identifiers (of course you then also cannot use the new source-level features).

– AJM Mar 17 at 10:45 @AJM: Yes, though that of course requires you to update your source completely to Java 5 (which isn't too bad, just rename identifiers that collide with new keywords). – Michael Borgwardt Mar 17 at 10:59 Great, thanks for your help. – AJM Mar 17 at 12:13.

This table shows several incompatibilities at the source (build-time) level between ejb 2.0, 2.1 and 3.0 versions, although binary (run-time) compatibility is supported for all releases, i.e. You can run your code on the new ejb versions without the need to recompile.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.