Wednesday, June 02, 2004
Politically Charged EJB Decision Hands a Victory to JBoss
Politically Charged EJB Decision Hands a Victory to JBoss "The EJB 3.0 expert group seems to have handed JBoss the EJB application server market on a silver platter. Several weeks ago at TheServerSide Java Symposium in Las Vegas the EJB expert group announced its decision to shelve the current entity bean architecture and focus on the lightweight persistence of Plain Old Java Objects (POJOs). Specifically, it decided to use Hibernate as the persistence mechanism in EJB 3.0. Hibernate is an open source object/relational mapping solution that joined the JBoss Group last year."
Subscribe to:
Post Comments (Atom)
1 comment:
(Bob)>> This is really interesting, but I wonder if it will become part of mainstream J2ee products. And I have to wonder if the development model for Hibernate isn't backwards for most enterprise apps.
Hibernate seems to start with the Java objects (POJOs), and then achieve a relational mapping against some target rdbms. But don't most enterprise apps start with the db schema, and then generate entity beans that make sense for that schema?
The other question that the article didn't address (and which I didn't find in a light scan of the Hibernate site) was, is Hibernate purely a persistence thing? And if so, how does this replace EJBs when a big part of what EJBs do is transaction management?
And even if the persistence model in Hibernate is a good one (meaning, easy to use, robust and fast), does that imply that persisted POJOs become automatically clusterable? And if the answer is yes, is it a good clustering model? For example, you can achieve clustering by storing everything in one database (the Microsoft/.net model), but is that always the best way to go? WebSphere persists EJBs across multiple nodes without relying on a single shared database.
Post a Comment