>
>In my oppinion, the BluePrint actually defines two incompatible use-models,
>just a few sections apart - one in the perspective of entity beans as an
>ORDB framework and one in the perspective of EJB Entity Beans as distributed
>objects:
>
>[Sun J2EE Blueprint, section 5.2] "An entity bean represents an object view
>of business data stored in persistent storage or an existing application.
>The bean provides an object wrapper around the data to simplify the task of
>accessing and manipulating it."
>
>[Sun J2EE Blueprint, section 5.3.1] "...Therefore modelling every object
>representing a row in the database as an entity bean is not recommended. An
>entity bean is better suited to represent a coarse-grained business object
>that provides more complex behaviour than only get and set methods for its
>fields."
>
>So even Sun has a hard time finding a use-model for EJB Entity Beans :-)
>
I don't think that'w what the Blueprints are saying at all. WHen they use
"coarse-grained" in this context, they mean use methods that update several
fields at once, like setCustomerData() or makeDeposit(), instead of twerpy
little get/set methods that cuase massive numbers of transactions for every
Entity bean emthod like setFirstName(), setLastName(), etc.
Ken Litwak
===========================================================================
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".
