Lines 189-194
Link Here
|
189 |
is <code>false</code>, this attribute will have no effect.</p> |
189 |
is <code>false</code>, this attribute will have no effect.</p> |
190 |
</attribute> |
190 |
</attribute> |
191 |
|
191 |
|
|
|
192 |
<attribute name="deployIgnorePaths" required="false"> |
193 |
<p>A comma-separated list of regular expressions of paths to |
194 |
<em>ignore</em> for <code>autoDeploy</code> and |
195 |
<code>deployOnStartup</code>. This allows you to keep your configuration |
196 |
in a version control system, for example, and not deploy a .svn or CVS |
197 |
folder that happens to be in <code>appBase</code>.</p> |
198 |
<p>These regular expressions are relative to <code>appBase</code>. They |
199 |
are also <em>anchored</em>, meaning the match is performed against the |
200 |
entire file/directory name. So, <code>foo</code> matches only a file or |
201 |
directory named <code>foo</code> but not <code>foo.war</code>, |
202 |
<code>foobar</code>, or <code>myfooapp</code>. To match anything with |
203 |
"foo", you would use something like <code>.*foo.*</code>.</p> |
204 |
<p>From a performance standpoint, a single regular expression using |
205 |
alternation will be more efficient than separate regular expressions. |
206 |
For example, <code>deployIgnorePaths</code> set to |
207 |
<code>foo\.war|bar</code> has the same effect as |
208 |
<code>foo\.war,bar</code>, but the former is more efficient.</p> |
209 |
<p>See <a href="#Automatic Application Deployment">Automatic Application |
210 |
Deployment</a> for more information.</p> |
211 |
</attribute> |
212 |
|
192 |
<attribute name="deployXML" required="false"> |
213 |
<attribute name="deployXML" required="false"> |
193 |
<p>Set to <code>false</code> if you want to disable parsing the context |
214 |
<p>Set to <code>false</code> if you want to disable parsing the context |
194 |
XML descriptor embedded inside the application (located at |
215 |
XML descriptor embedded inside the application (located at |
Lines 337-350
Link Here
|
337 |
<code>ROOT.xml</code>.</li> |
358 |
<code>ROOT.xml</code>.</li> |
338 |
<li>Any web application archive file within the Host's <code>appBase</code> |
359 |
<li>Any web application archive file within the Host's <code>appBase</code> |
339 |
directory that has not already been deployed as a result of a context |
360 |
directory that has not already been deployed as a result of a context |
340 |
XML descriptor and does not have a corresponding directory of the same |
361 |
XML descriptor, does not have a corresponding directory of the same |
341 |
name (without the ".war" extension) will be deployed next. The context |
362 |
name (without the ".war" extension), and is not excluded by |
342 |
path used will be a slash character ("/") followed by the web |
363 |
<code>deployIgnorePaths</code> will be deployed next. The context path |
343 |
application archive name less the ".war" extension. The one exception to |
364 |
used will be a slash character ("/") followed by the web application |
344 |
this rule is that a web application archive named "ROOT.war" will be |
365 |
archive name less the ".war" extension. The one exception to this rule |
345 |
deployed with a context path of <code>/</code>. Multi-level contexts may |
366 |
is that a web application archive named "ROOT.war" will be deployed with |
346 |
be defined by using #, e.g. use a WAR named <code>foo#bar.war</code> for |
367 |
a context path of <code>/</code>. Multi-level contexts may be defined by |
347 |
a context path of <code>/foo/bar</code>.<br/> |
368 |
using #, e.g. use a WAR named <code>foo#bar.war</code> for a context |
|
|
369 |
path of <code>/foo/bar</code>.<br/> |
348 |
If the <code>unpackWARs</code> attribute is <code>true</code>, the web |
370 |
If the <code>unpackWARs</code> attribute is <code>true</code>, the web |
349 |
application archive file will be expanded to a directory of the same |
371 |
application archive file will be expanded to a directory of the same |
350 |
name (without the ".war" extension".<br/> |
372 |
name (without the ".war" extension".<br/> |
Lines 363-373
Link Here
|
363 |
</li> |
385 |
</li> |
364 |
<li>Finally, any sub-directory within the Host's <code>appBase</code> that |
386 |
<li>Finally, any sub-directory within the Host's <code>appBase</code> that |
365 |
has not already been deployed as a result of a context XML descriptor |
387 |
has not already been deployed as a result of a context XML descriptor |
366 |
will be deployed. The context path used will be a slash character |
388 |
and is not excluded by <code>deployIgnorePaths</code> will be deployed. |
367 |
("/") followed by the directory name, unless the directory name is ROOT, |
389 |
The context path used will be a slash character ("/") followed by the |
368 |
in which case the context path will <code>/</code>. Multi-level contexts |
390 |
directory name, unless the directory name is ROOT, in which case the |
369 |
may be defined by using #, e.g. use a directory named |
391 |
context path will <code>/</code>. Multi-level contexts may be defined by |
370 |
<code>foo#bar</code> for a context path of <code>/foo/bar</code>.<br/> |
392 |
using #, e.g. use a directory named <code>foo#bar</code> for a context |
|
|
393 |
path of <code>/foo/bar</code>.<br/> |
371 |
If <code>copyXml</code> is <code>true</code> (it is <code>false</code> |
394 |
If <code>copyXml</code> is <code>true</code> (it is <code>false</code> |
372 |
by default), any directory within the Hosts's <code>appBase</code> |
395 |
by default), any directory within the Hosts's <code>appBase</code> |
373 |
directory that does not have a corresponding context XML descriptor in |
396 |
directory that does not have a corresponding context XML descriptor in |
Lines 420-434
Link Here
|
420 |
|
443 |
|
421 |
<p>When using automatic deployment, the <code>docBase</code> defined by |
444 |
<p>When using automatic deployment, the <code>docBase</code> defined by |
422 |
an XML <a href="context.html">Context</a> file should be outside of the |
445 |
an XML <a href="context.html">Context</a> file should be outside of the |
423 |
<code>appBase</code> directory. If this is not the case difficulties |
446 |
<code>appBase</code> directory. If this is not the case, difficulties |
424 |
may be experienced deploying the web application or the application may |
447 |
may be experienced deploying the web application or the application may |
425 |
be deployed twice.</p> |
448 |
be deployed twice. The <code>deployIgnorePaths</code> attribute can be used |
|
|
449 |
to avoid this situation.</p> |
426 |
|
450 |
|
427 |
<p>Finally, note that if you are defining contexts explicitly in server.xml, |
451 |
<p>Finally, note that if you are defining contexts explicitly in server.xml, |
428 |
you should probably turn off automatic application deployment. Otherwise, |
452 |
you should probably turn off automatic application deployment or specify |
429 |
the web applications will each be deployed twice, and that may cause |
453 |
<code>deployIgnorePaths</code> carefully. Otherwise, the web applications |
430 |
problems for the applications. |
454 |
will each be deployed twice, and that may cause problems for the |
431 |
</p> |
455 |
applications.</p> |
432 |
|
456 |
|
433 |
</subsection> |
457 |
</subsection> |
434 |
|
458 |
|