This seems to be a similar problem to the persistancy policy that
is distributed with FoodSmart, a sample GemStone/J application.
The idea is to create a persistancy facade, or in this case a
communication facade (?) that would use a policy to determine
if you make an EJB or an RMI call.
Kirk
-----Original Message-----
From: Ashwin Dinakar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, February 07, 2000 10:48 AM
Subject: EJB/RMI Run time switch
>Hi all,
> I want to be able to switch between EJB and RMI code at run time.
>I have basically an interface extending Remote for RMI which lists the
business methods to be implemented and I do the same thing with EJBObject
for EJB.
>Does anyone here have nice design patterns for this type of problem ?
>Code samples would be appreciated.
>
>Thanks,
>Ashwin.
>
>===========================================================================
>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".
