Yes, not a nice feature change: -:( But the deployment system at
tomcat 5.5 has changed a lot, and I switch to easier way to get
FarmWarDeployer up and running (Tomcat 5.5.5 Release 12/04).
Last year nobody of the community ask for the separate depoyDir
feature and so this was not at my top prio list.
My missing feature list at FarmWarDeployer
- support for Engine level configuration that we support multiple hosts
- separate deployDir from host appBase dir
- control application activation
currently all application start a very strange way when async
sender is used.
- give the user the changes that sessions are exists after redeployment!
- JMX Support
I am now fix the ROOT.war bug. I hope Tim and Filip can test it with
svn head.
Thanks
Peter
Am 31.03.2006 um 23:40 schrieb Filip Hanik - Dev Lists:
Tim Lucia Wrote:
and a more recent post from Peter Rossbach saying that it SHOULD
be the
appBase.
[http://marc.theaimsgroup.com/?l=tomcat-user&m=113828526109819&w=2]
On Thursday 26 Jan 2006 11:33, Peter Rossbach wrote:
Please, set the deployDir to your webapps dir.
Peter
ha ha, :) Peter has a habit of changing underlying functionality to
new functionality, but provide no backwards compatibility. Earlier,
the FarmWarDeploy used to deploy remote .war files that were
located in any directory. (ie deployDir)
Peter has changed this functionlity, that you now must deploy into
the appBase dir, definitely a functionality I don't like and would
have -1 if I had caught the change.
Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
