This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes Object Relational Mapping and the fly likes EJB3 = the future Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » Object Relational Mapping
Bookmark "EJB3 = the future" Watch "EJB3 = the future" New topic
Author

EJB3 = the future

jim cato
Greenhorn

Joined: Jul 15, 2008
Posts: 21
Hi,

Some would say that EJB have so far failed to deliver an efficient standard portable solution to data access.

Do you think that the latest incarnation, EJB3, does achieve this and furthermore will underpin data access strategies in the future?

To what extent are EJB3 covered in the book?

Cheers,
Jim
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968
    
    1

I think JPA, which really supplants "entity beans" in EJB3.0 will really be embraced by the JEE5 community.

One problem is simply the delay in getting JEE5 Application Servers out there. So many people are using ORM tools like Hibernate already, that waiting for JEE5 application servers to come out and provide them what they need just isn't practical. And we all know that once a technology takes root, it's tough to get rid of it.

I mean, not too many people are switching away from Windows on the desktop, regardless of how many people might argue that there are better alternatives. Coming late to the dinner table is often the difference between being adopted or not, regardless of the strength or weakness of the technology itself.

-Cameron McKenzie
Roland Barcia
author
Ranch Hand

Joined: Apr 15, 2004
Posts: 181
I would not say EJB is a failure. I would say Entity Beans may have been a failure. We cover JPA, which I think will have success because it takes into account patterns used by TopLink, Hibernate, JDO, and others.

The book is on the persistence layer, so we do not focus alot on EJB 3. We discuss how using JPA in a managed environment like EJB 3 can make things easier in some scenarios, by allowing automatic propagation of the Persistence Context. I know other frameworks like Spring can give you similar advantages. But in general, I feel EJB 3 is a good thing.


Roland Barcia: IBM Distinguished Engineer, CTO Mobile for Lab Services
 
GeeCON Prague 2014
 
subject: EJB3 = the future