Hi guys,
I was looking at this issue on WL 4.5 and I wasn't really happy with their
"hot deploy" feature. There are so many issues that have to be looked in
here:
What do you do for redeploying when:
1. Bean implementation is the same , only XML descriptor is changed?
2. Interfaces are same, actual method implementations change?
3. Interfaces change.
4. Combinations of above.
Maybe Rickard,Marc,Juha,Oleg and Dan should look really closely into this
one and come up with some draft?
Best,
Vladimir
On Fri, 12 May 2000, Rickard [iso-8859-1] �berg wrote:
> Hi!
>
> Pedro Mota wrote:
> > I have a question (maybe a newbie question) :
> >
> > What happens when I redeploy a bean (a session bean for example)
> > and there is one (or more) client connected to one (or more)
> > instance/s of this bean?
> >
> > (a) The bean is destroyed and the client disconnected
>
> Yes.
>
> > (b) The client continues to work with the bean until it calls
> > remove()... upcoming clients work with "new beans"?
> >
> > (c) more imaginable scenarios... :-?
> >
> > -----------------------------------------------------------------
> > If the answer is (a) then I have another question...
> >
> > What happens to any pending transaction? They are rolledback?
>
> When the first bean is undeployed the distribution layer plugin should
> stop all incoming requests and wait until any pending ones are done.
>
> (uhm.. this is presently not happening..)
>
> /Rickar
>
> --
> 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]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
