June 11, 2003

EJB 3.0

There is a new JCP proposal JSR-220 for Enterprise JavaBeans 3.0. Something about it was bothering me, but I couldn't put my finger on it until I wrote another blog post earlier today.

If you read the spec proposal (and the other J2EE specs in general, I guess) there is no real separation between the EJB programming model and the EJB runtime environment / model. The vast majority of the changes in the JSR-220 proposal effect the programming model, but this is not being done by layering this as an abstraction layer on top of the existing runtime, but by completely reving everything.

Personally, I would have expected the EJB runtime foundation to have stabalized by now, and not being constantly reved and altered. All future enhancements could, and should, be built out using extensibility points, rather than changes to the core - that's the only good way to build a solid and stable runtime platform IMHO. I believe it is perfectly possible to layer the new trendy development concepts like aspects and metadata onto the existing runtime, for example.

It seems to me that this is exactly the same problem mentioned about Web Service proxies - not keeping a clear separation between the runtime and programming models leads to increased confusion among architects, developers and users.

Of course, J2EE is both a development and a runtime platform, but to achieve ease-of-development improvements does not necessarily have to be tied to changes in the runtime too - unless of course you want to guarentee a constant stream of upgrade revenues, I guess.

Entry categories: J2EE
Posted by Jorgen Thelin at June 11, 2003 01:29 PM - [PermaLink]
 
Comments
This is not hard to workout. I guess the analogy could be word - I do not see how you can expect the richer functionality of word2000 to fit into the same format as word95. Without lots of conversion programs, or using a blotted format like rtf. Having said that they really should have thought a lot further ahead than they did when producing the EJB1.0 specification - both relational or OO2RDB issues were not new at the time. Also I really don't think the spec writers were focused on revenues, as the specs read in places like theoretical exercises. Posted by: Sailesh Panchal on September 26, 2003 06:42 AM