Hi Kevin
You seem to be missing the big picture here. With using a Servlet engine for
handling all your logic you are putting all your eggs the same basket. You
may have partitioned your logic up in the servlet container envirionment
(MVC) but this is only at class level. EJB gives you distinct partioning at
the component level. If you model all your Data and business logic at the
EJB level then you create yourself a reuseable component layer. This way you
can connect to this EJB layer from any clients, (Java) Servlets, (Java) jsp
, (java) desktop client , (java) mobile client, (VB) desktop client, (CORBA)
client and many more. At the moment you can only access your model layer
through the servlet contain (or at least you can't easily access the same
model from servlets and standalone clients, due to classloading etc)
When you are accessing DB's from servlets you find yourself reinventing the
wheel , for OR mapping, calling frameworks and data caching algorithims all
the things that the best (like orion) app servers support
:)
-----Original Message-----
From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 6:22 PM
To: Orion-Interest
Subject: EJB vs Servlets
Hey all,
I know this is a little off-topic, but seeing as how Orion is about the only
fully compliant EJB server, I figured this would be a better place to ask.
Lately I have talked to a number of people that have been moving towards EJB
and pulled back because they have found it to be more tedious to develop, as
well as the end result was slower than just using Servlets.
I ask this because it appears to me that the servlet engine (at least with
2.2) being able to be failed over, load-balanced, etc, seems to be quite as
capable for scalability and fault-tolerance as the ejb engine used to be. I
do realize that the EJB container offers transaction management, but
connection pooling is available in the servlet engine at the server level as
well. So, if you lose speed in development time and performance, what is the
real benefits of moving to EJB? I should say this with caution..I am sure
the EJB engine/container offers some things the servlet container doesn't,
but I would think its possible to actually put those abilities in the
servlet container.
Anyways..I'll be interested in hearing any feedback on this.
Thanks.
