Hi,
In fact this is a common requirement in enterprise class applications, where
you often need to use different "strategies" to handle the same problem -
e.g. for order placement, credit card validation etc etc,
Make sure you parameterize for flexibility though.
Parameterization, in this respect, is more necessary for the Home interface,
through which you regulate creation than for the Remote interface through
which you would access business services.
Or you can "build" different beans exposing the same interfaces but restrict
yourself during "deployment" to a particular one.
Sandeep Dath.
----- Original Message -----
From: "Rickard Öberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 08, 2001 6:14 PM
Subject: Re: Multiple beans with the same interface
> Andrés Aguiar wrote:
> > I have a set of Session Beans that have the same interface. Is there any
way
> > to avoid to have to write a Remote/Home class for each one?
>
> Sure, just use the same remote/home class for all of them.
>
> /Rickard
>
> --
> Rickard Öberg
>
> Email: [EMAIL PROTECTED]
>
>
===========================================================================
> 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".
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.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".
