Comments on: JDO and EJB join forces: The cat is out of the bag http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag blogging about life, the universe, and everything tech Fri, 04 May 2012 14:57:05 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Dion http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag/comment-page-1#comment-8922 Dion Mon, 27 Sep 2004 01:27:34 +0000 http://almaer.com/blog2/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag#comment-8922 Cedric - This surprises me, as it hasn't been my experience. I have been on many projects where we really wanted to change the persistence manager. For example, being stuck with WebSphere and wanting something better than their CMP. What normally happened was one of two things: - Shoot, we are stuck with their damn CMP (since management has mandatted CMP) - We can get away from this... let's use JDO where we can CHOOSE the damn vendor depending on our needs (or end up using Hibernate) Since everyone will be moving to this ONE persistence API, I think it makes OBVIOUS sense to make it so you can plugin the vendor that you wish! However, I totally understand the app server vendors don't want this :) Dion Cedric -

This surprises me, as it hasn’t been my experience.

I have been on many projects where we really wanted to change the persistence manager.

For example, being stuck with WebSphere and wanting something better than their CMP.

What normally happened was one of two things:

- Shoot, we are stuck with their damn CMP (since management has mandatted CMP)
- We can get away from this… let’s use JDO where we can CHOOSE the damn vendor depending on our needs (or end up using Hibernate)

Since everyone will be moving to this ONE persistence API, I think it makes OBVIOUS sense to make it so you can plugin the vendor that you wish!

However, I totally understand the app server vendors don’t want this :)

Dion

]]> By: Cedric http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag/comment-page-1#comment-8921 Cedric Sat, 25 Sep 2004 23:52:48 +0000 http://almaer.com/blog2/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag#comment-8921 The annotations are definitely staying. As for the pluggable persistence manager, we've had this since WLS 5.0 (!) but we phased it out because, simply put, nobody ever used it, so I question your assertion that a lot of people want that... -- Cedric The annotations are definitely staying.

As for the pluggable persistence manager, we’ve had this since WLS 5.0 (!) but we phased it out because, simply put, nobody ever used it, so I question your assertion that a lot of people want that…

–
Cedric

]]> By: Carlos Sanchez's Weblog http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag/comment-page-1#comment-8923 Carlos Sanchez's Weblog Sat, 25 Sep 2004 19:08:04 +0000 http://almaer.com/blog2/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag#comment-8923 <strong>JDO and EJB join forces</strong> Dion wrote an interesting entry about the joining of JDO and EJB . A new spec is being created to provide an unified persistence API for both standard and enterprise java editions using POJ Os. JDO and EJB join forces

Dion wrote an interesting entry about the joining of JDO and EJB . A new spec is being created to provide an unified persistence API for both standard and enterprise java editions using POJ Os.

]]> By: Dion http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag/comment-page-1#comment-8920 Dion Sat, 25 Sep 2004 18:44:31 +0000 http://almaer.com/blog2/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag#comment-8920 Gabriel - JDBC isn't hidden away. There are provisions for this via: a) You can grab a JDBC connection within the same TX context b) You can use SQL as the query language Dion Gabriel -

JDBC isn’t hidden away. There are provisions for this via:

a) You can grab a JDBC connection within the same TX context
b) You can use SQL as the query language

Dion

]]> By: Jason Carreira http://almaer.com/blog/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag/comment-page-1#comment-8919 Jason Carreira Sat, 25 Sep 2004 17:26:49 +0000 http://almaer.com/blog2/jdo-and-ejb-join-forces-the-cat-is-out-of-the-bag#comment-8919 Any idea if it's still going to be dependent on 1.5 with annotations? And are those annotations going to be defined and jar'd in the j2ee.jar? Will I have to compile against the j2ee.jar or a vendor jar and either ship with the j2ee.jar or deploy in a container just to get the annotation classes? This is what worries me about it being based on the current EJB 3.0 work and living in the EJB JSR. Any idea if it’s still going to be dependent on 1.5 with annotations? And are those annotations going to be defined and jar’d in the j2ee.jar? Will I have to compile against the j2ee.jar or a vendor jar and either ship with the j2ee.jar or deploy in a container just to get the annotation classes?

This is what worries me about it being based on the current EJB 3.0 work and living in the EJB JSR.

]]>