If Rickard thinks it is, I would ask you to open a Bugzilla "feature"
and own it Pedro (in jBoss 2.0 ;-)
:-)
marc
[EMAIL PROTECTED] wrote:
>
> Rickard �berg wrote:
> >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
>
> Hi Rickard,
>
> I don't know how much overhead this will add to each method call but I
> think it's an area it can be tuned a lot.
>
> Dreaming... dreaming... I have seen it would very interesting to have
> different options when you undeploy a bean. I see two options :
>
> (1) "Soft undeploy" -> Old clients continue working with "old beans"
> until they disconnect, then the bean is
> destroyed. I think this only applies to
> stateful beans.
>
> (2) "Hard undeploy" -> Old clients are disconnected, old beans destroyed
> and any pending transaction is completed. This
> applies to all kind of beans (stateless, stateful
> and entities).
>
> Option (1) will be useful if you have made a change in the code and you
> want your clients use it ASAP but without forcing a disconnection in
> current clients.
>
> Option (2) will be very useful when the change made to the code, doesn't
> allow to coexist (is correct this word?) old code with new code, a
> dangerous situation if you have old clients talking to old code and new
> clients talking to new code.
>
> I can imagine even a third option, but I don't know if it would be
> possible :
>
> (3) "Terminator undeploy" -> Old clients are disconnected, old beans
> destroyed and any pending transaction
> rolled back.
>
> And maybe a message like this is showed on the screen... "Hasta la
> vista baby" :-D
>
> Is interesting this idea?
>
> Pedro Mota
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
