On Aug 2, 2008, at 8:40 AM, Karan Malhi wrote:
Another thing I was thinking is that we might be able to come up
with some
way to disable the EJB 3.1 functionality for those who need to be
guaranteed
they're only using EJB 3.0 or lower.
This is a good idea. A system property like openejb.compliance=3.0 .
We
could default it to 3.0 and have people switch to 3.1 if they need
the 3.1
functionality.
On Aug 2, 2008, at 9:09 AM, Karan Malhi wrote:
Meant to say,default is 3.1
Right. That'd be one we'd want to enable on a per ejb module basis
via the openejb-jar.xml properties.
Would be nice to see something released soon. Our examples on our
download
page are already old and some do not work because of bugs (which are
already
fixed in trunk) or dependencies on versions which do not exist in
repositories.
I think the webservice example is the only one that will cause
problems, but that's enough. We also have way more examples than we
do html pages to accompany them.
Overall, release wise I'd like to get the last of the singleton stuff
in and add the no-interface bean view and then get rid of asm as a
dependency by using the shade plugin.
-David
