Web-app-deploy
From Resin 3.0
(Difference between revisions)
Line 21: | Line 21: | ||
|- | |- | ||
||expand-directory||The directory where archives are expanded||path | ||expand-directory||The directory where archives are expanded||path | ||
+ | |- | ||
+ | ||expand-prefix||Prefix to generate the expanded directory||"" | ||
+ | |- | ||
+ | ||expand-suffix||Suffix to generate the expanded directory||"" | ||
|- | |- | ||
||url-prefix||Prefix for any URL access||none | ||url-prefix||Prefix for any URL access||none |
Revision as of 00:46, 31 January 2006
The <web-app-deploy> tag configures the webapps directory, i.e. a location where you can drop .war files and have them expanded to web-apps.
Essentially, it's an automatic directory for <web-app> tags with archive-path attributes.
For example, in the default resin.conf, if you drop a foo.war in server.root/webapps, it will expand to webapps/foo and be browseable at http://www.foo.com/foo.
It's also possible to create a Web Application without a .war files by creating a directory in the webapps without
... <web-app-deploy path="webapps"/> ...
attribute | description | default |
path | The location for both expansion directories and archives | none |
archive-directory | The location for archive (.war) files | path |
expand-directory | The directory where archives are expanded | path |
expand-prefix | Prefix to generate the expanded directory | "" |
expand-suffix | Suffix to generate the expanded directory | "" |
url-prefix | Prefix for any URL access | none |
expand-cleanup-fileset | List of files to delete on redeploy | delete entire archive |
require-file | additional files which will force a reload | none |
startup-mode | starting mode of deployed web-apps | automatic |
redeploy-mode | mode for checking an redeploying web-apps | automatic |
web-app-default | default configuration for all web-apps | none |
web-app | overriding configuration for any deployed webapps | none |