Actually, I know all about it. I have read up on it in those books and
others. Infact, we have already separated our code into those tiers but it
all runs in the servlet engine. This is what I am talking about. I am using
the Struts framework to allow all forms submitted to a single controller
servlet, which then calls upong action classes. Those action classes then
figure out what "session" class to call upon. These "session" classes are
our logic (ejb) code, but its not in the EJB container..it runs in our
servlet engine. It is separated, just not from the servlet engine itself.
However, by compexity of building EJBs, I think I mean what goes into it.
Instead of a single class, we would have 2 (or is it 3) interfaces and an
implementation class. To access it, its not as simple as a class/reference
variable to an object in the servlet engine, you have to do a lookup,
etc..its a bit more code. Sure..its not terribly complex, but compared to
doing it the way we are now, there is quite a bit more work involved than
what we are doing now. Also, actually testing and learning how exactly it
works is a process that will take a little time. All of these things add up.
What I am wondering is..is it really worth it if supposedly EJB doesn't
offer much in the way of performance..it just separates the logic into a
separate "tier" of servers. Our code is already separated long those tiers
now..and it will probably be easier for us to move to EJB than those that
have logic in their servlets.
> -----Original Message-----
> From: Russ White [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 09, 2000 11:32 AM
> To: Orion-Interest
> Subject: RE: EJB vs Servlets
>
>
> 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.
> >
> >
>
