> Considering you mentioned using entity beans, what do you mean by a
careful
> design of the persistence layer?  Isn't that layer provided by your EJB
> container?  And if you wrote another persistence layer, then why EJBs?

No.  A persistence layer (or at least a good one) is not mandated.  Yes in
1.0 you had BMP and with 1.1 you have CMP, but there is nothing stating that
you must have complex mapping available.  Trivial/Useless 1:1 Entity to
Table mapping can be supplied and that meets, or more commonly providing a
mechanism for a persistence layer to inject itself into your container.

With 2.0 comples mapping, and how a persistence layer gets called by the
container is specified.

Does that answer it?

Thor HW

===========================================================================
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".

Reply via email to