I concur. I use this pattern of info transport and it has been extremely
successful. Depending on your info "wrapper" design, you'll have access to
metadata as well. One thought I'll add is that this pattern is equally
applicable in both directions (mutator as well as accessor).
> -----Original Message-----
> From: Richard Monson-Haefel [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, February 25, 1999 12:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Question regarding Session and Entity Beans
>
> Excellent points, Sriram!
>
> A paper I wrote on the use of tabular data for the EJB workshop describes
> some implementation options for returning ResultSets, arrays, or other
> tabular types of data to the client. The tabular data strategies are meant
> to be used when a session bean needs to provide complex data to the client
> without exposing the underlying object model. I've used them successfully
> in
> both Java RMI and CORBA projects.
>
> It can be found at:
> http://www.inprise.com/events/ejbdesign/submissions/tabluar_data.html
>
> Richard
>
>
>
> -----Original Message-----
> From: Sriram Srinivasan
> To: [EMAIL PROTECTED]
> Sent: 2/25/99 2:03 PM
> Subject: Re: Question regarding Session and Entity Beans
>
>
>
> Look at the session bean as a representative of the client on the
> server, instead of as a public wrapper for the entity bean. So, if
> the UI displays a list of customer names and addresses, you could
> (should) have a method on the session bean that returns an array
> of customer related data, either formatted as a ResultSet or an
> array of "CustomerInfo" objects .. your choice. The UI should
> not dwell on the structure of the object model.
>
> ==========================================================================
> =
> 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".
