Hi!
Jeremiah Johnson wrote:
> Is there defined behavior for a hot re-deploying a jar which happens to replace an
>instance of a bean that is involved in a transaction? Does that question make sense?
> To rephrase, if I fix a bug in a stateful session bean and I redeploy the
>application containing that session bean, do I have to be concerned about trying to
>time my redeploy so that no clients are making calls to an instance of the bean?
Well, an undeploy will shut down the containers and the invocation
layers. I guess we could add code in "stop" that makes sure that when
"stop" returns no invocations are active, and no invocations are let in.
So no, currently it is not well-defined, but we could change that.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
