You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by pi...@apache.org on 2002/05/05 05:30:42 UTC
cvs commit: jakarta-tomcat-connectors/webapp/docs building.xml index.xml style.xsl
pier 02/05/04 20:30:42
Modified: webapp build.xml
webapp/docs building.xml index.xml style.xsl
Log:
Some more documentation in index.xml.
Fixed little hole in the stylesheet not translating <a> tags,
Updated the build.xml file since javadoc gets executed _all_
the time.
Revision Changes Path
1.5 +2 -2 jakarta-tomcat-connectors/webapp/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 5 May 2002 02:24:26 -0000 1.4
+++ build.xml 5 May 2002 03:30:42 -0000 1.5
@@ -3,7 +3,7 @@
<!--
"Coyote" connector framework for Jakarta Tomcat
- $Id: build.xml,v 1.4 2002/05/05 02:24:26 pier Exp $
+ $Id: build.xml,v 1.5 2002/05/05 03:30:42 pier Exp $
-->
@@ -203,7 +203,7 @@
</javadoc>
</target>
- <target name="docs" depends="javadoc"
+ <target name="docs" depends="prepare"
description="Create Documentation">
<copy todir="${build.home}/docs" >
<fileset dir="./docs">
1.2 +3 -2 jakarta-tomcat-connectors/webapp/docs/building.xml
Index: building.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/docs/building.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- building.xml 5 May 2002 01:58:22 -0000 1.1
+++ building.xml 5 May 2002 03:30:42 -0000 1.2
@@ -28,8 +28,9 @@
Multi-threaded support has now been added since the multi threaded
environment is now available also under UNIX based operating systems via
Apache 2.0, therefore the only things left to do are a little bit of
- porting (not much, since the WebApp module is based on the , which does
- most of the job for you) and a lot of testing.
+ porting (not much, since the WebApp module is based on the
+ <a href="http://apr.apache.org/">Apache Portable Runtime</a>
+ library, which does most of the job for you) and a lot of testing.
</p>
<p>
1.3 +62 -3 jakarta-tomcat-connectors/webapp/docs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/docs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 5 May 2002 02:24:26 -0000 1.2
+++ index.xml 5 May 2002 03:30:42 -0000 1.3
@@ -10,7 +10,29 @@
What is the WebApp Module
</description>
- <todo/>
+ <p>
+ Do you remember the old times of <b>mod_jserv</b>? Maybe you're too
+ young, but I do pretty well. At that time, the amazing <b>Apache
+ JServ</b> servlet container didn't have an HTTP stack per se, but
+ rather relied on the Apache 1.2 and 1.3 web server to have clients
+ accessing it.
+ </p>
+
+ <p>
+ And this is when a "module" came into the picture: a module such
+ as <b>mod_jserv</b> or the <b>WebApp</b> module connects the HTTP
+ stack of the front end web-server(s) with one or more instances of
+ a servlet container in the back end.
+ </p>
+
+ <p>
+ The WebApp module does exactly that, it's not finished (it might
+ never will), but it works, and it works pretty damn good. Plus (this
+ comes for free), we tried very hard to keep the internals clean and
+ well-designed, so that it will be so easy for anyone to simply provide
+ patches in case of bugs (yes, there are some!).
+ </p>
+
</section>
<section title="Purpose">
@@ -18,7 +40,24 @@
Why should I use the WebApp Module?
</description>
- <todo/>
+ <p>
+ Because we say so? Not kidding, but it's really up to you, there are
+ several alternatives to "do the job", when we started this project
+ all of them were (in our not-so-humble-opinion), a pile of crap.
+ </p>
+
+ <p>
+ Lately there have been some improvements on those alternatives, and
+ probably, if you're wondering why you want to try out WebApp, you should
+ really stop reading now, and go and download something else.
+ </p>
+
+ <p>
+ If instead you're an adventurous geek who's up for a challenge, skip
+ the rest of this document and go to the <a href="building.xml"/>
+ section, there's where the fun starts.
+ </p>
+
</section>
@@ -27,7 +66,27 @@
Are there alternative ways to connect Apache and Tomcat?
</description>
- <todo/>
+ <p>
+ It would NOT be fair not to talk about our lovely (???) competitors,
+ of course, otherwise someone might even start calling us names, so,
+ in brief, you can use the following alternatives:
+ </p>
+
+ <p>
+ <b>Tomcat's internal HTTP stack and mod_proxy</b>, which is not that
+ bad, but slow, well, of course Tomcat didn't have 8/9 years of C
+ routine optimization like the Apache Web Server, but it's quite good.
+ The only disadvantage I see is that it looks pretty ridiculous to
+ parse an HTTP request to generate it again (exactly the same), and
+ to parse again the response to send it back unchanged... Anyway.
+ </p>
+
+ <p>
+ <b>mod_jk</b>, is the same of the WebApp module, if you're wondering
+ why you should be using the latter instead of the former, well, I
+ believe I already answered this question (forget about WebApp).
+ </p>
+
</section>
</document>
1.3 +1 -1 jakarta-tomcat-connectors/webapp/docs/style.xsl
Index: style.xsl
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/docs/style.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- style.xsl 5 May 2002 02:24:26 -0000 1.2
+++ style.xsl 5 May 2002 03:30:42 -0000 1.3
@@ -239,7 +239,7 @@
</xsl:template>
<xsl:template match="p">
- <p class="section"><xsl:apply-templates select="b|text()"/></p>
+ <p class="section"><xsl:apply-templates select="b|a|text()"/></p>
</xsl:template>
<xsl:template match="b">
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>