Implementing EJB 1.1 or EJB 2.0 on top of JORM are two possibilities.
The plans are indeed that JOnAS implements EJB 2.0 in the future.
However, from what we have heard, it seems that the evolution of the
EJB 2.0 spec is going to less transparency/less orthogonality w.r.t. persistence
for CMP than it is currently in EJB 1.1 (in EJB 1.1, the CMP bean
programmer does not have to treat persistent attributes any differently
from other attributes).
On top of the EJB 2.0-supporting container for CMP, our objective is
also to implement another container with more transparency for the bean
programmer (more in the line of the EJB 1.1 spec regarding transparency/orthogonality).
alex
John Sharley wrote:
Sounds good. How is this likely to relate to the developing EJB 2.0 spec
?> Here are the current JOnAS status and plans regarding CMP.
>
> The current version 2.0 of JOnAS does not provide persistent
> references between CPM entity beans, and neither polymorphism
> between CPM entity beans (which is not in the EJB 1.1 spec).
>
> We, at France Telecom R&D, are working on a flexible and adaptable
> persistence layer called JORM (for Java Object Repository
> Mapping). We plan to integrate JORM with JOnAS this summer, and we
> should expect enhanced CMP before the end of the year.
>
> Features of this new layer for CMP entity beans will include:
> - persistent inter-bean references;
> - polymorphism of bean classes;
> - management of multi-valued attributes (lists, sets, arrays).
>
> In a first step, only an implicit object-relational mapping will be
> provided.
> Extensions will include a more flexible object-relational mapping,
> mapping to other types of data sources (object databases).
-- Note: the address [EMAIL PROTECTED] should not be used. Instead, please use [EMAIL PROTECTED], or [EMAIL PROTECTED]
