Warning: going to spin acronyms on you and use EJB3 to refer to the new EJB3 Simplified API and JPA to refer to the new javax.persistence API. I swizzled the subject to reflect.

On Feb 3, 2006, at 8:22 AM, Andrus Adamchik wrote:

On Feb 3, 2006, at 7:02 AM, Jacek Laskowski wrote:


And, what are your plans for EJB3?

Noone has yet stepped in and been working on it. There're works to
simplify the process of developing EJB 3.0 container.

Hi folks,

We at Cayenne project (http://objectstyle.org/cayenne/) are planning to build EJB 3 compatibility in the framework for the next major release. I would love to cooperate with ObjectEJB developers as our efforts are complimentary (OpenEJB providing the container and "traditional" EJBs and Cayenne - the ORM part of the spec).

It's excellent to hear that Cayenne is going to implement JPA.

OpenEJB is definitely going to support EJB3 and any implementation of the JPA that is license friendly.

In the fantasy land in my mind, there will be many JPA Providers out there and OpenEJB will support them all via the standard mechanism for an app specifying it's desired PersistenceProvider.

We don't yet have the code that plugs in a JPA Persistence Provider, so that would be the first thing we'd need to work on.

On Feb 4, 2006, at 11:52 AM, Andrus Adamchik wrote:
On Feb 4, 2006, at 7:07 AM, Jacek Laskowski wrote:
Why not. You can start developing the integration right away. When you
get started, let us know about it ;) Ask questions and move on. I'm
sure more people will eventually jump in and help implementing it.

Makes sense. On our end we will probably start by creating a javax.persistence.spi.PersistenceProvider facade to the current (non-EJB3) Cayenne API. I need advice where and how we can plug this to OpenEJB, and is this even possible at this point?

Not quite sure just yet. Have to do some more reading on my end on what it takes to support an implementation of a JPA PersistenceProvider. I've put up a confluence page just now to help collaboration.

  http://docs.codehaus.org/display/OPENEJB/EJB+3+Whiteboard

Something a little more permanent than email for keeping discussion notes.

One caveat I can see at the moment is that OpenEJB 3 will/may require JSE
5 or retroviewer or retrotranslator are used.

I haven't seen any official Sun statements on whether J2EE 1.5 should work with JDK 1.4, but common sense tells me "no, it can't", cause it relies on JDK 1.5 features. So is it even an issue with OpenEJB (or Geronimo for that matter)? I mean if the spec says 1.5, why maintain 1.4 compatibility in the *new* releases?

I think with something like retrotranslator, suppport for JDK 1.4 is low hanging fruit so to speak. Tomcat maintains support for JDK 1.4 and allowing that crowd to still use OpenEJB 3 would be a plus. We also want OpenEJB 3 to be an upgrade path from OpenEJB 1, so maintaining some JDK 1.4 support is great if we can.

Not a hard requirement, just a nice to have.

In Cayenne this *is* an issue as it works as a standalone engine that is not tied to a particular J2EE spec version. We addressed the need to support JDK 1.5 and still provide a big subset (99%) of functionality for 1.4 users by splitting the code in two subprojects, with cayenne-1.5 dependent on cayenne-1.4:

You should checkout retrotransaltor. Digging into it now myself. I hear impressive things about it such as it being able to run the JAXB2 reference implementation which can't be easy.


-David

Reply via email to