Here's my take on it.
In EJB 2.0 JDO could only be used for BMP, and I doubt very well at that.
It uses a different query language than what is spec'd out for EJB2.0
JDO will be post processed on classes with changes made so that the class
verifiers and security should still work.
There are some implementations based on the current jdo, from another
standards group, which is a pre-process implementation, which I like a bit
more (never quite comfortable with black magic).
The new JDO spec requires adherence to a baseline of functionality that will
be available from all compliant jdo managers, but it also support
extensions. These extensions should "just not fire" if deployed on another
vendors jdo manager.
IMHO you'll see the O/R mappers continue to provide value as they are
injected into the server layer via the mechanisms described in the EJB2.0
spec. I don't see how JDO will fit in nicely (different query languae, post
processing, etc.) with other containers and sctrict verifiers.
Thor HW
----- Original Message -----
From: "Martin Heinzl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 04, 2000 9:15 AM
Subject: AppServer , EJB and JDO ??
> Hi
>
> I would like to know what the different AppServer and EJB vendors are
> thinking
> about the new Java Data Object specification (JDO) which is still under
> development.
>
> JDO has been designed to work in an EJB environment and JDO provides
> transparent persistency for entity beans.
>
> JDO identifiers handles the persistent identification of objects.
> Furthermore JDO distinguishes
> between First Class and Second Class objects. Which as far as I
> understood it maps
> pretty good to Entity beans and dependend objects.
>
> So if I look at the possibilities today and the upcoming possibilities
> like the new Java Connectors API, integration of different O/R mapping
> tools
> into some of the Application Server and the new persistency model in
> EJB2.0
> then I would like to know how this fits into the picture.
>
> Is this additional added value or is it a competitor for the connectors
> API and the EJB2.0 persistence model ?
>
>
> Thanks and best regards
> Martin
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
