Cedric Beust wrote:
>
> These are the real tricky issues and I don't think there is a standard way of
> proceeding. Some elements of response:
>
> - clients holding stubs to remote objects should receive a
> NoSuchObjectException (being silently redirected to a new instance is probably
> not the best idea, but a point can be made for that as well)
If it's a stateless session bean (or an entity bean). a new instance is
perfectly reasonable.
> - the real problem lies in in-flight transactions. You can choose to rollback
> them all right away (the easy way) or wait for them to time out. It all
> depends how sophisticated you want your deployment to be
As long as your app server design caters for in-flight transactions and
stateful session beans, this is a non-issue.
> There are also several possible scenarios to make the new homes available to
> existing clients.
I think that any decent implementation would be transparent to clients.
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
