You should read up on J2EE so you can understand what separation of
data/logic/presentation is all about. I would recommend any of the O'Reilly
books on the subject(s). Also Development of EJBs is very simple. Especially
with a good IDE like VA, Forte, or JBuilder. Orion even comes with a simple tool
for creating very useful EntityBeans from a GUI.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin
> Sent: Monday, October 09, 2000 1: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.
>
>
