To make the context documentation page more readable, I suggest replacing the last preformatted block on the page with something like the following:

<div class="wrapped-code">
<code>
&lt;Context path="/mywebapp" docBase="/Users/theuser/mywebapp/src/main/webapp"&gt;

<div>
&lt;Resources
<p>className="org.apache.naming.resources.VirtualDirContext"</p>
<p>extraResourcePaths="/WEB-INF/classes=/Users/theuser/mywebapp/target/classes,<wbr>/pictures=/Users/theuser/mypictures,<wbr>/movies=/Users/theuser/mymovies"</p>
<p>/&gt;</p>
</div>

<div>
&lt;Loader
<p>className="org.apache.catalina.loader.VirtualWebappLoader"</p>
<p>virtualClasspath="/Users/theuser/mywebapp/target/classes;<wbr>/Users/theuser/mylib/target/classes;<wbr>/Users/theuser/.m2/repository/log4j/log4j/1.2.15/log4j-1.2.15.jar"</p>
<p>/&gt;</p>
</div>

<div>
&lt;JarScanner scanAllDirectories="true" /&gt;
</div>

&lt;/Context&gt;
</code>
</div>

with the corresponding style rules:

<style type="text/css">
<!--
.wrapped-code div { margin: 1em 0 0 1em; }
.wrapped-code p { margin: 0 0 0 2em; text-indent: -1em; }
.wrapped-code code { background-color: transparent; }
-->
</style>

The results may be compared with the original in the following locations:

    http://www.tmbsw.com/tomcat/html/context.html
    http://tomcat.apache.org/tomcat-7.0-doc/config/context.html

A more readable version of the HTML source is available here:

    http://www.tmbsw.com/tomcat/html/context.formatted.html

It may make sense to add a note indicating where spaces are and are not allowed in the attribute values.

What browser versions is Apache documentation required to support? I've tested on IE7 and recent versions of Firefox and Chrome. The text-indent style rule and <wbr> HTML element may be a problem on legacy browsers.

How would I go about submitting something like this?

-Terence Bandoian


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to