It's a _rule_ on any project I am running!
There are lots of consequences in the resulting context. How to distribute
state of objects to clients, etc...
We have document many of the consequences in our best practices stuff...
-Chris.
> -----Original Message-----
> From: Smith, Curt H. [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 31, 2000 8:54 AM
> To: [EMAIL PROTECTED]
> Subject: Re: OO Analysis and Design for EJB Systems
>
> > I know the best practices for using EJBs are still developing
> > but lets not
> > forget the (often hard) lessons learned from RMI/CORBA. You
> > must be very
> > careful about the design of the remote interfaces. All the
> > component models
> > use remote interfaces for the components so buyer beware :-)
>
> Some have offered in this list, a magazine author and my own
> tact is to always design a client side facade for the BO
> interface. I'd offer this as a std EJB practice. Never
> allow the client side to ctx.create() ... obj.methods().
> This exposes server architecture and makes change expensive.
>
> What do you think about the client side facade as a _rule_ ?
>
>
> curt
>
>
> Curt Smith
> Z-Tel
> email: [EMAIL PROTECTED]
> work: 404-237-1166 x182
> FAX: 404-237-1167
>
> ==========================================================================
> =
> 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".
