This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Howdy all, I just wanted to pass this on. It is from the Sun engineer who is the lead developer of the J2EE container for the Reference Implementation. This is their view of things... First off, it's important to clarify that EJB vs. JDO isn't really a correct comparison. � It makes sense to compare CMP vs. JDO (and JDBC for that matter) but EJB is about much more than just support for persistence. � Regarding JDO, it will definitely be considered for inclusion in the J2EE 1.5 platform but considering the JSRs for J2EE 1.5 haven't even been filed yet it's too early to know where the expert group and the community as a whole stand on the matter. Like any java technology, it's important that developers tell their J2EE vendors which features are most important to them in the future. � Finally, the focus of EJB 3.0 (and J2EE 1.5 as a whole) will be ease of use. � The next release will simplify many of the things that are often perceived as making EJB too complex. For example, it will move much closer to the "POJO" model, so that most of the callbacks that are now required to be implemented(e.g. ejbLoad/ejbStore) will be optional. � There will also likely be support for component inheritance, which is often pointed to as a major deficiency vs. JDO and other persistence mechanisms such as Hibernate. � There will also be a major effort to reduce or remove the reliance on deployment descriptors from the developer's view, in favor of both meta-data and intelligent defaulting. � � � �As with anything else, �no single technology is best suited for all tasks, but I certainly think there's plenty of future for CMP and EJB.
So there you go. The way the J2EE team views the topic... and believe me, the fact that this guy even wrote me back was something of a miracle, because of how BUSY they are trying to get J2EE 1.4 out the door. Everytime I see how busy the J2EE team is, it makes me realize how much activity and business there is around EJB. And that can only be good cheers, Kathy
Thanks for sharing it. Any idea about the enhancements that will be made to EJB-QL in EJB 3.0? Like, will there be a support for SELECTing multiple columns in a resultset? Also, will there be a new type of bean for web services? What are your views?
For example, it will move much closer to the "POJO" model, so that most of the callbacks that are now required to be implemented(e.g. ejbLoad/ejbStore) will be optional. There will also likely be support for component inheritance, which is often pointed to as a major deficiency vs. JDO and other persistence mechanisms such as Hibernate.
This is great news. I stongly feel that Entity beans must be made more light weight so that it can compete with JDO,Toplink and Hibernate.