old apis out, new frameworks in, where is Java EE 6 heading?

[fahd helwani]

Hi guys,

it's a great effort what you are doing here by hosting all these authors, keep it up

meanwhile I got couple questions to Mr Mick Knutson: after taking a look at the book and going through the index and few pages available on amazon, I'm wondering about the things: first in the case of the removal of lots of old apis "Which you listed some of them like JAX-RPC" what will happen about backward compatibility? does it mean that over time the old J2EE applications will be absolute and won't work? doesn't that violate the fact that Java maintained backward compatibility all these years?

my second question is about all the frameworks that can be integrated into Java EE 6, I remember back in the old days that JPA came as a standard for all the persistence frameworks that took away lots of complexity of the persistency in Java EE? do you think that by time such new frameworks, especially the scripting languages, will become part of Java EE, or even take over major parts of it? if these are used as extensions, will they find their way into the framework eventually?

thank you again.
Fahd

[Mick Knutson]

fahd helwani wrote:
meanwhile I got couple questions to Mr Mick Knutson: after taking a look at the book and going through the index and few pages available on amazon, I'm wondering about the things: first in the case of the removal of lots of old apis "Which you listed some of them like JAX-RPC" what will happen about backward compatibility? does it mean that over time the old J2EE applications will be absolute and won't work? doesn't that violate the fact that Java maintained backward compatibility all these years?

Oracle states that at some point these will be removed. I dont think that maintaining backward compatibility in the future versions of the Java EE spec will be possible.
At some point, projects that wish to upgrade to newer versions of the Java EE spec will have a certain amount of re-factoring involved.

fahd helwani wrote:my second question is about all the frameworks that can be integrated into Java EE 6, I remember back in the old days that JPA came as a standard for all the persistence frameworks that took away lots of complexity of the persistency in Java EE? do you think that by time such new frameworks, especially the scripting languages, will become part of Java EE, or even take over major parts of it? if these are used as extensions, will they find their way into the framework eventually?

thank you again.
Fahd

I think other frameworks are the drivers for many of the Java EE standards. CDI has roots in Spring and Guice. JPA has roots in hibernate and iBatis.

[megan smith]

"I think other frameworks are the drivers for many of the Java EE standards. CDI has roots in Spring and Guice. JPA has roots in hibernate and iBatis. "

So does JAVA EE6 have all features Spring offers?

[Mick Knutson]

megan smith wrote:

"I think other frameworks are the drivers for many of the Java EE standards. CDI has roots in Spring and Guice. JPA has roots in hibernate and iBatis. "

So does JAVA EE6 have all features Spring offers?

No.
But CDI is a form of dependency injection just like Spring.

[fahd helwani]

Thanks Mick