> -----Original Message-----
> From: Imre Kifor [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, May 16, 1999 8:52 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Real advantage of session bean wrappers?
>
[Frentress, James] <snip>
> >In many applications the view uses multiple model instances. If the
> client
> >works directly with the entity beans, then the client has to get a
> reference
> >for each entity bean instance. If you wrap the entities with a session
> bean,
> >then the client only needs one reference. The session bean manages all of
> >the references to the entity instances. This approach definitely reduces
> >resource requirements (one OUT reference versus many OUT references).
>
>
> This sounds very nice on paper, however, in practice that one session bean
> very fast becomes a monolith, you loose flexibility and, most importantly,
> you are forced to ignore encapsulation (and all the other advances in
> OOP).
[Frentress, James] BINGO. this was the first indication that i
wasn't going to like this route in the first place.
> Imre Kifor
> Valto Systems
>
[Frentress, James] are you sure we haven't met? seems like i've
known you for years ;)
>
===========================================================================
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".
