A trivial testcase is to simply start the bundle with the tomcat-test.ear in the deploy directory and then touch the ear after startup. I see the same basic behavior with both the 2.4.0.26 JBoss tomcat and jetty bundles, and neither does a double deployment. ----- Original Message ----- From: Julian Gosnell To: [EMAIL PROTECTED] Sent: Monday, August 13, 2001 5:47 PM Subject: Re: [JBoss-dev] problems with latest jboss-jetty? Marc, I'd be interested to know if the same version of JBoss with TomCat exhibits this double deployment problem - otherwise it is something that I should be looking at..... Jules _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
- [JBoss-dev] problems with latest jboss-jetty? marc fleury
- Re: [JBoss-dev] problems with latest jboss-jetty? Julian Gosnell
- Re: [JBoss-dev] problems with latest jboss-jetty? Julian Gosnell
- Re: [JBoss-dev] problems with latest jboss-jetty? Scott M Stark
- Re: [JBoss-dev] problems with latest jboss-jet... Julian Gosnell
- autodeployer bug RE: [JBoss-dev] problems ... marc fleury
- RE: autodeployer bug RE: [JBoss-dev] ... Vincent Harcq
- RE: autodeployer bug RE: [JBoss-dev] ... Jim Brownfield
- Re: autodeployer bug RE: [JBoss-d... Scott M Stark
- Re: autodeployer bug RE: [JBo... Julian Gosnell
- Re: autodeployer bug RE: [JBo... Scott M Stark
- RE: autodeployer bug RE: [JBo... marc fleury
- Re: autodeployer bug RE: [JBo... Scott M Stark
- Re: autodeployer bug RE: [JBo... Julian Gosnell
