[snip]
> To use entity beans well, it seems (to my understanding anyway) that
> I would design the persistent object structure, and then pick the
> points at which I want to provide a distributed interface, with the
> associated transaction, synchronization, security, and life cycle
> support. I make those object interfaces entity beans.
>
> As you point out, sometimes these interface points are at the head
> of either a collection or graph of associated objects, and won't
> necessarily map one-to-one to a business object.
>
[snip]
> -Paul Hodgetts
>
BINGO! I agree 100%. EJB is a component model, not an object model.
Please read original very interesting post, to avoid noise with such
a short reply to a long message, I've snipped most of it...
Frank Sauer
===========================================================================
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".
