I would say we remove it. We already have a CMP over JPA implementation, however if you can point out where you are going to make the change to remove castor jdo, then i can document it so that if need be, we can plug it in later.
On 6/26/07, David Blevins <[EMAIL PROTECTED]> wrote:
On Jun 26, 2007, at 12:09 PM, Dain Sundstrom wrote: > Does anyone mind if I drop castor jdo for CMP in OpenEJB 3.0? I > think this will allow for a nice simplification of the CMP over JPA > code, and will further reduce our dependencies. Since castor > doesn't support EJB-QL and managed relationships, it wasn't tested > in during the JEE certification work so, I doubt it works properly > anymore. > > If the castor team complete a JPA implementation, we will be able > to support it via our existing CMP over JPA engine. I think that's the most important question now that I give it some thought, i.e. who is willing to support it. I certainly don't want to. Maybe we retire it but leave the CMP over JPA code alone (i.e. be ready to put it back) for a release or two to see if people complain about it not being there. -David
-- Karan Singh Malhi
