Remy Maucherat wrote:Fixing the bug is rather annoying, and the amount of stuff which should be automated is quite big, and seems not worth it.
Instead, I'd like to remove local deploy from the manager servlet (IMO, it's useless). If using the Ant tasks to do a local deploy, then it's up to you to persist the config later, upon the user's choice.
+0
I can confirm it can't be done automatically, because when deploying from a configFile, there's no way to know what context is being deployed. And it wouldn't work anyway as the XML would be saved to the original config file location.
I'll have to add code in StandardContext to have it move its config file to the config base if there's one and it's outside the config base.
For the last case, (WAR file + no config file + unpackWAR == false), the config file will have to be saved automatically after deploying (which should work, as the context path is known).
I think we should also add some Ant tasks:
- a "save config" Ant task - with a context parameter allowing to save just one context (this task is also useful when using the JMX tasks to reconfigure Tomcat, and persisting the config is needed)
I've added the new /save mapping and code. Coding the corresponding action is trivial.
- maybe extend a bit the JMX tasks
+1
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
