Hello Kevin,
Well, inofficially, 1.1.4 does include support for most of the EJB 2.0
OR-mapping and support for message-driven beans as well as certain changes, like
abstract accessor-methods for entity beans.
However, it's very beta and we're developing some examples for it and testing it
internally before officially launching it.
EJB 2.0 requires the container to be fully EJB 1.1 backwards compatible, so you
can rest assure that your EJB 1.1 beans still will work. The server
automatically detects whether it's an EJB 1.1 bean or an EJB 2.0 bean.
This means that we do not need 2 seperate branches, thus not having any problems
of bug-fixes being left out of a certain version.
Regards,
Karl Avedal
Kevin Duffey wrote:
> I am curious, being that there have been some problems noticed with the 1.0
> release, and fixes are coming out, do these updates also include the latest
> work on say EJB 2.0, and the likes? Or is that a separate "branch" of the
> project slated for say, Orion 2.0?
>
> The reason I ask is that if the work on EJB 2.0 is being included in the
> latest 1.1.4 update (and later), that might cause some problems with
> backwards EJB 1.1 support. So I am curious if the Orion team is working on a
> separate branch for the EJB 2.0 support (most likely J2EE 1.3 version), and
> the current branch for updates/fixes of Orion 1.0. Lastly..if you are doing
> the two separate branches, do you continually merge the 1.0.+ fixes into the
> 2.0 version so that those getting the latest to test out EJB 2.0 (if you are
> even releasing that yet) get the latest fixes in the previous versions.
>
> Thanks.
