Hello Evan,
> > The problem is not that CMP implementations do not support this, but the problem
>is that it is not standadized how this is done until EJB 2.0. The means that you
> > can not use these features and easily give your Enterprise Archive to another
>person who can deploy it in their server without any add-ons.
> >
> > Executive summary: The features are already there, but EJB 2.0 makes it all
>portable
>
> It would be nice if that were true. Check section 10.2.3 (in public draft):
>
> A FROM clause can consist only of correlation variable declarations that are based
>on valid path expres-sions
> originating from the entity bean�s abstract schema. A FROM clause cannot specify
>arbitrary
> �joins�; it can only designate allowable declarations based on the abstract schema
>of the entity bean and
> navigations allowed from the abstract schema.
>
I did not say that you can do arbitrary joins with EJB 2.0. What I said is that it
takes us away from the simplest model of one ejb - one table, which is the only
portable way in EJB 1.1. What's interesting is not the SQL you can write or have
generated, but what the data model allows you to do in terms of solving real problems,
and EJB 2.0 allows complex object relationships, which is the important thing.
However, I agree that the EJB 2.0 specification is not complete in the area. In
particular I would want all standard types of Collections to be usable, especially Map,
which is not supported so far by the EJB 2.0 draft.
Regards,
Karl Avedal
The Orion Application Server (http://www.orionserver.com)
===========================================================================
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".
