Of course. It corresponds to using the deploy task. After deploying, the WAR should be in the host appBase.
I might be on crack again but my WAR doesn't get copied over to the host appBase (webapps). If I set unpackWARs to true the war gets unpacked into its directory under webapps.
Local deploys do not copy the WAR over. So, as with TC 4.1, you have to save the config if you want it persisted (the difference with TC 4.1 is that if unpackWAR is true, then it is also used for webapps deployed through the manager, which causes the automagic persistence after restart). There's not much choice here ... Maybe save the context file (and only that) automatically by using the Server.storeContext thingie in case of a local deploy (reminder: the save-to-XML needs to be refactored).
I'm talking about the "Upload a WAR" which will copy the WAR to the appBase.
(please, don't always try to use the only situation which causes trouble) (please vote to my lame ballots)
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
