> 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.

No, I am not the one making all the decisions. Those are made by the jBoss
board along with communication with the jBoss user and developer
communities.

I merely expressed the facts regarding the scope of our project and how it
would relate to OpenEJB. I also strongly questioned some of your statements,
but that was more of a personal reflection.

> 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.

jBoss already has pluggable security and JAAS integration, transaction
services, and pluggable persistence managers (our own, TOPLink, and CocoBase
currently). We are also working on the Connector API and EJB 2.0 support
including MessageDriven beans.

Plus a whole lot more, including administration tools and a pretty darn
advanced clustering system.

> 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.

Excellent! I will await the results eagerly.

PLGC,
  Rickard

ps. BTW, "PLGC" is the jBoss way of saying "alright, enough yadda yadda,
let's back to coding" and means "Peace, Love, and Good Code".




Reply via email to