Charles,
See responses inline below.
-krish
>Hi, I have some EJB RemoteException questions and hope
>that someone will have answers to them. Let's say I
>have bean A and bean B. Bean A is calling bean B's
>remote method.
>Case 1. Bean A and Bean B resides on the same server.
>Are we guaranteed to not receive any RemoteException
>exception since they are running in the same server?
No - in the case of EJB 1.1, it does not matter. A
EJB 1.1 compliant container has to throw a RemoteException
if one occurs - irrespective of the processes in which
the EJBs reside. See changes in EJB 2.0 specification (PFD 2)
for information on exceptions thrown by Local Interfaces.
>Case 2: Bean A and Bean B in different server but in a
>clustered environment.
>If B is a stateless session bean, does that mean the
>container will automatically create a new B in a
>different server to serve the method instead of
>throwing the RemoteException?
>Or will the container still throw the RemoteException
>and expect me to recreate B and call the method again?
>Or is it dependent on the vendor?
Whether a new object will be created on a different server
in the cluster depends on your EJB vendor implementation.
For example: with the Borland AppServer, remote references
of stateless, stateful and entity beans will failover to
another server. You will have to check with your EJB vendor
and/or documentation to see how clustering and fail-overs
are handled. The topic of clustering and fail-overs
are not covered in the EJB specs (both 1.1 and 2.0 pfd 2)
===========================================================================
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".
