Hi Kenji,
Kenji Konaka wrote:
>
>I've read the doc - I've never really have done the
>RMI-IIOP stuf, but this was interesting - thank you
>very much.
>
Well I think that's the point - you don't ever have to "do RMI/IIOP" -
you just do RMI since that's the interface. IIOP is only the protocol
but since it *may* be the protocol the Application Server is using (you
have no way of knowing at runtime), you need to take into consideration
the limitations imposed in 1.4.12 of that spec to be safe. Relying on
any distributed gc involving references being passed into EJBs is making
a possibly incorrect assumption about the app server implementation.
>
> > In practice, even if the EJB is passivated and reactived, the reference
> > to the remote object should still be valid unless the remote server has,
> > in the meantime, decided to destory it using
> > PortableRemoteObject.unexportObject(object)...
>
>ok., so it's more like no plain vanila RMI callbacks
>are recommended in this(EJB's) case... got it,got it...
>
Kind of I meant :) You can't be sure the App server is using vanilla
RMI-JRMP (with dgc) or RMI/IIOP or RMI over some other protocol to
communicate with the callback object so don't rely on dgc. Callbacks
will work fine and can be recommended depending on the nature of your
application (you might be better off using JMS for example). But
because the app server may be using RMI/IIOP the important point is the
callback object reference lifecycle is the responsibility of the client
VM - you shouldn't rely on dgc. If the client is an EJB, then let the
client app server manage the EJB's lifecycle but if the client is a
simple RMI server object, you need to manager the callback object's
lifecycle explicitly (from within the client VM) using
PRO.unexportObject().
j.
===========================================================================
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".
