On Thu, 14 Oct 2004 14:54:52 +0000 (UTC), Derek Mahar <[EMAIL PROTECTED]> wrote: > Remy Maucherat <remy.maucherat <at> gmail.com> writes: > > > > On Wed, 13 Oct 2004 21:38:00 +0000 (UTC), Derek Mahar <dmahar <at> penson.ca> > wrote: > > > Shapira, Yoav <Yoav.Shapira <at> mpi.com> writes: > > > > > > I should mention that originally, I did not have antiJARLocking enabled, but > > > enabling both antiJARLocking and antiResourceLocking does not appear to have > > > made any difference. > > > > This works for me. I don't find you convincing at all, overall. > > > > Then I'll just have to be more convincing. Note that in the following scenario, > I deployed and then undeployed in two distinct operations. The first deploy was > successful. I then ran my application, terminated the session by invoking tag > <session:invalidate/> in taglibs-session.jar, invoked an undeploy, which > Ant/Tomcat reports as successful, and then attempted a deploy, which Ant/Tomcat > reports as failed. I found that Tomcat removed context file billing.xml and > billing.war, but left behind taglibs-session.jar and the billing work folder. > See details and additional commentary below. Contents of context file > billing.xml and <billing:logout> tag are at the very end.
The only thing I am willing to look at is a ready to run WAR. -- xxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
