Richard Monson Haefel wrote:
>I have a different view point from Ian's. Most listing and summary data
is
>specific to a scenario and is not generally reusable. For this reason I
prefer
>to use direct database access from a session bean that represents the
>scenario. In other words, I agree with Tim's third option. I would say
that
>this is an appropriate strategy for 3 reasons: 1) Its more peformant to
access
>the database directly for read-only listing and summary data. 2)
Encapsulation
>is achieved through the session bean (to say its not is to say that entity
bean
>encapsulation is some how superior), 3) most listing and summary needs are
not
>reusable and should therefor not reside in the entity bean.
I must have higher aims for encapsulation than Richard! To me
"encalsulating" the data inside two beans is not encapsulation.
Also, I believe that summary extraction will quite often be reusable.
Indeed one could imaging providing a general query service in which the
selection criteria and fields needed could be passed as parameters.
Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069
===========================================================================
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".
