JDO will work with BMP.
EJB's already build support classes, but they DO NOT do post processing of
the *.class files as JDO will. That is very, very different.
There are actually 3 query languages on the go.
JDO which is designed to be closer to the languages semantics.
JMS
EJB2.0 which is based on JMS and sql (i think sql92 and not sql3)
Thor HW
----- Original Message -----
From: "Martin Heinzl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 05, 2000 2:33 AM
Subject: Re: AppServer , EJB and JDO ??
> Hi Thor
>
> Thanks a lot for your response. As JDO is still under development
> I am wondering why they want to integrate a different query language ?
> Would it not make much more sense to use the EJB query language ?
>
> On the other side as far as I understand the EJB2.0 persistency model,
> in EJB2.0 the container or better the development/deployment tools also
> have to do some postprocessing in order create a concrete implementation
of the
> bean class as there are abstract base definitions in the EJB2.0 CMP model.
>
> In one article I read about JDO (Java-Report June2000) there was mentioned
> that JDO was designed to work with EJB. Therefore I cannot really
understand
> why they are going for different query languages, ....
>
> Regards
> Martin
>
>
> Thor Heinrichs-Wolpert wrote:
>
> > 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
>
>
===========================================================================
> 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".
