A very effective technique can be to use an OODMS (e.g. ObjectStore,
Objectivity) rather than entity beans, and then code session EJBs to
encapsulate logic. I've never liked O/R mappings. It's a constant disappoint
to me that EJB doesn't generically support the transparent mapping of entity
EJBs to an OODB, although BMP could emulate it with careful use of the ODMG
API's. I know that this is basically what ODI's Javlin module does, but
that's a platform-limited product.
- Joshua Goodall
-----Original Message-----
From: Kyle Cordes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 8:51 PM
To: Orion-Interest
Subject: Re: EJB vs Servlets
This strikes me as a straw-man argument. There is no reason that servlet
code must use JDBC directly. There are many object-wrapper products
available that work similarly to CMP beans; such products predate EJB by a
long, long time.
-Kyle Cordes
----- Original Message -----
From: Mike <mailto:[EMAIL PROTECTED]> Cannon-Brookes
To: Orion-Interest <mailto:[EMAIL PROTECTED]>
Sent: Monday, October 09, 2000 6:08 PM
Subject: RE: EJB vs Servlets
I use EJBs in a high volume environment and have had no problems with
scalability or speed yet.
I have to say once you know EJBs well enough, dev't is definitely faster
than with servlets. The sheer volume of JDBC code and debugging required in
a servlet outweighs the quick speed you can do the same thing in EJBs. (See
ejb-maker for an example).
Mike
