1. Does anyone have success undeploying/redeploying a wicket .war to a remote tomcat (5.5.x, poss. 6.x) instance, without cycling tomcat? (eg, using mvn tomcat:deploy or ant with the tomcat deployment components)
It looks like the undeploy is not happening 100% - the app name continues to appear in the list, no matter how the undeploy step happens. 2. If not (1), can any developer comment on whether this is a known issue, and if it might be addressed any time soon or how a n00b might tackle it and / or what might wicket be doing to hamper undeployment? (I didn't see anything in the bug db). Without this capability (which exists with all the other frameworks we use), we cannot use wicket. We have many other unrelated web-apps running in the same tomcat instance and obviously to cycle those (because tomcat has to start/stop without live redeploy) is a non-starter in my org. Thanks - Steve
