I am not precisely clear on what you mean by composing based on Principal.
Rather than look for some magical formula here, our idea at the moment is to
take a more simplistic (and perhaps brute force) approach. A client
requiring a particular set of services uses a session bean to get at those
services. The session beans return object value holders to the client,
depending on use case. We have no intention to attempt to swizzle what is
returned to the client based on Principal. Frankly, this sounds messy.
-Chris.
> -----Original Message-----
> From: punit malik [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, August 18, 1999 4:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Inheritance and EJB
>
> Chris,
> >This is interesting, but is it always the case that you want all of the
> >serialized state of sampleData returned to the client?
>
> Since sample data is based on composition pattern, I think one can change
> it dynamically depending on Principal.
>
> Punit
>
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
> ==========================================================================
> =
> 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".
