Javier Borrajo wrote:
> Current EJB 1.1 limitations means EJB is suitable for OLTP and not
> many more scenarios. It is clearly not suitable for workflow,
> asynchronous messaging, parallel processing, ...
Quite right. This is unfortunate, as stateless session beans could
really assume these duties quite easily if the specification would allow
it. Mandating JMS is the first step, but is certainly not the final
step.
> We use several mechanisms to keep SQL out of our Java classes.
> No need to use CMP entity beans to get SQL-less Java.
Quite right. When JDO comes out you'll see a dramatic drop in usage
growth for EJB, since many people are investing in EJB solely for its
pseudo-specified O/R mapping stuff.
> For example an XML file
Or a basic text file! XML need not be used for everything in the world.
> mapping Java classes and fields to
> DB tables and columns, including lookup tables, 1..N relationships,
> search criteria, etc. Very fast development achieved. Just get an XML parser
> and develop a simple O/R mapper.
No such thing. Buy (http://www.thoughtinc.com/) or download
(http://castor.exolab.com/) one instead. See
http://www.ambysoft.com/mappingObjects.pdf.
Cheers,
Laird
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
