I read the article too and IMHO what he is trying to do requires two
components, an entity object that represents the business domain
Customer object and a session object to perform the calculations
and other operations on collection of Customers.
If you wanted to perform the business process of promoting an
Employee's grade, do you ask the Employee object to do it or a
secured Session object, bearing in mind that there may be related
operations involved, such as increasing his salary?
> -----Original Message-----
> From: Karl-Fredrik Blixt [SMTP:[EMAIL PROTECTED]]
> Sent: 28 June 1999 09:36
> To: [EMAIL PROTECTED]
> Subject: ObjectWatch Newsletter Number 20
>
> Hi all!
>
> I just read the first part of the chapter from Roger Session's book in
> ObjectWatch Newsletter Number 20 (http://www.objectwatch.com/issue20.htm).
>
> I don't see how he interprets the customer as executing on behalf of a
> single
> client:
>
> 'But on the other hand, credit limit calculations do not represent any
> direct
> view of data in the database, so maybe we are dealing with a session bean.
> And
> this functionality seems to "execute on behalf of a single client,"
> whatever
> that means.'
>
> Surely there can be many clients accessing this functionality, why should
> it
> only be one? Does anybody know what he might be thinking?
>
> /Kalle
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
