Far from being a hypothetical question, we're inviting you to post your questions to Linda DeMichiel, co-spec lead for JSR 220, Enterprise JavaBeans 3.0. Artima will be interviewing Linda in the coming days as part of our JavaOne special content, and we'd like to have your EJB 3 questions answered, too.
The JCP executive committee recently approved four specifications that define the next version of the Java EE platform:
The "umbrella JSR" for Java EE 5, JSR 244: Java Platform, Enterprise Edition 5 (Java EE 5)
As part of Artima's special JavaOne coverage, we will interview Linda DeMichiel, co-spec lead of JSR 220. In preparation for our interview, we'd like to ask for your questions: What would you ask Linda about EJB 3 and the new EJB persistence model?
Submit your questions here, and then make sure to check back here often, or subscribe to the Artima Newsletter to be notified when our interview appears.
In EJB3, unlike previous EJB Spec, lots of aspects like transaction, referential integrity, and table identifer are designated by annotation. Though annotations are good because we can opt of out XMLs, I believe that those annotations still needs to be modified from time to time to reflect design modifications. I strongly believe that there will be a lot of changes especially in the initial development stage.
Unlike XML based approach which only requires to modify XML files, annotation based approach requires to open some Java file, and then modify the source code, and then compile sources again.
That being the case, doesn't annotation based approach imply more compilations and development time?
a)How is EJB# different from Hibernate ? Is EJB3 not a wrapper on Hibernate ? b)What does EJB3 lack with respect to hibernate. I heard Gavin King mentioning about concept of "Filtering of Entities" . Does EJB3 support it?
>> Microsoft's LINQ looks like a very promising technology, will we see anything similar on the Java world?
Doubtful. I'm sure Microsoft has a patent on this technology which they invented in 2005. I think it's called O/R mapping. There was a flush of technology coming out of Redmond in that year. They invented something called N-Tier technology, and realized everything they had done to date assumed one computer, one man, one software vendor, no security risks, no scalability issues. Thank God they were able to see past 2005 well in to the future (say, 1994)... wait, that's the past.