I have CCed jboss-dev so that they are aware of my response to your post on our
mailing list.
Rickard Oberg wrote:
> So, to sum up the jBoss project has absolutely no intent on integrating with
> the OpenEJB container system. Why? Well, why would we? AFAICT there are
> really no reasons for us to use OpenEJB considering that the EJB container
> architecture we already have is well-designed, stable, and performance
> tuned.
Well, what can I say. Since you are the one making all the decisions for the
jBoss community it would probably do me little good to argue the point. I think
my last e-mail states all the advantages for using OpenEJB quite clearly. We're
not interested in pushing OpenEJB on any open source project that's not
interested in using it. That would be a fruitless and wasted effort.
OpenEJB will prove itself soon enough. Admittedly its not in first release yet
(still in development for EJB 2.0) so we have a little ways to go before its
ready for prime time. But with support for plugable security, transaction
services, Connector API, persistence managers, JMS providers for Message Driven
beans and adaptability to pretty much any application server, OpenEJB is going
to be pretty hard to beat.
Rather then argue about it, wait until OpenEJB is in final release. We'll plug
OpenEJB into the jBoss framework and performance test jBoss with its native
container against the OpenEJB plug-in. Regardless of the results I'll post them
for everyone to see.
Richard
--
Richard Monson-Haefel
Author of Enterprise JavaBeans, 2nd Edition (O'Reilly 2000)
Co-Author of Java Message Service (O'Reilly 2000)
http://www.EjbNow.com
