Hi!
[EMAIL PROTECTED] wrote:
> I am askingf myself if redeploying would be possible without
> destroying/disconnecting clients. This would be "increible"
> (can't translate my spanish surprise :-)
This isn't really as hard as you think.. I could do it right away, but
as always there are other consequences.
Possible solution:
Currently each container has its own ContainerInvoker RMI object. This
means that the following context info is sent, which determines which
bean that should be invoked:
* RMI Object OID
For each call we could send the URL of the deployment, changing the
context to:
* RMI Object OID of singleton invoker
* URL string + bean name
When the singleton invoker gets the call it can look in some hashtable
for the key {URL, EJB name} and invoke on the result.
So while the latter would allow clients to not disconnect on redeploy,
it does mean sending more contextual info on every call.
If anyone has a workaround, please let us know.
/Rickard
ps. hm.. perhaps a mapping between the URL string and a plain sequenced
number.. or use RMI Activation?
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.ejboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
