Java EE 6 is on the drawing board, but the opinions are already starting to diverge. Rod Johnson -- of Spring fame -- thinks Java EE 6 is on the right track, see the discussion on Rod Johnson: "Java EE 6 Gets it Right"
. However, this is not the same tone adopted by some OSGi proponents.
Peter Kriens over at OSGi writes: "Can someone tell Sun about OSGi", going onto say :
Someone just sent me a mail linking JSR 316. A JSR that will specify Java Enterprise Edition 6, the successor of Java EE 5, which was defined in JSR 244.
Now before we take a look, lets just investigate some recent trends in the Enterprise computing world. Hmm, BEA moved their micro Service Architecture on top of OSGi, IBM Websphere 6.1 seems to have chosen OSGi, Jonas is an EE framework build on OSGi from day one, and the JBoss Microcontainer is modified to support OSGi. On top of that, we have one product that made many people re-think Java EE: Spring. Now this product fell in love with OSGi. The market clearly says one size does not fit all. One would expect that these trends have some influence on Java EE 6? Sigh, think again.
Alex Blewitt, continues with his post "Sun submits JSR 316, still doesn't get OSGi", saying :
What's really interesting is that this approach (of combining lots of individual elements to one big package) mirrors what Sun's trying to do with the Java language. Instead of breaking units down into smaller and smaller levels (or bundles), they're going the opposite way and defining larger and larger chunks.
What are your thoughts on Java EE 6 ? Are the OSGi claims unfounded ? Or are they on the mark ?
Full post from Peter : http://www.osgi.org/blog/2007/07/can-someone-tell-sun-about-osgi.html
Full post from Alex :