You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mike Braden <mb...@utenzi.com> on 2001/03/15 16:29:08 UTC

[PATCH] TC 3.3 mod_jk-howto.html

This patch contains the updates as requested by Dan Milstein.

I've included the diff -u of the mod_jk-howto from cvs as .patch.gz.
I'm also including the .html doc.

The document has been slightly re-organized to group the Apache configs
together and separately group the Tomcat configs together.

The update for the <ApacheConfig /> directive is included with
a list of options and an example.

References and instructions were added for the new build scripts for Solaris
and hp-ux with references to IRIX and AIX builds.

The FAQ was updated with a reference on the DL archives and the user DL for
support as well as an apxs Q.  Hopefully this will help reduce some of the
newbie mod_jk Q's or at least direct them to the right place.

The next chance I get I'll work on the tomcat-apache-howto.html to make the
two docs more consistent.

Note: This document is in the context of TC 3.3.

This update includes Chris Pepper's changes as well - from Dan.


Mike.
--
Mike Braden
mbraden@utenzi.com
mikeb@mwbinc.com

From: Dan Milstein [danmil@shore.net]
Sent: Monday, March 12, 2001 11:48 PM
To: tomcat-dev@jakarta.apache.org
Subject: Re: [PATCH] Update to mod_jk-howto.html

Mike,

First off, thanks for working on this doc -- it's great to see someone
bringing the user docs for mod_jk up to date.

However, two things:

 1) If you can run 'diff -u' (if you've got it from cvs, 'cvs diff -u'), it
will produce the diff in "unified" format, which makes it possible to merge
changes via the patch program.  Without that, I'd have to apply things more
or less by hand.

 2) Chris Pepper actually submitted some fixes to this same doc (mostly
reformating the HTML and fixing typos), which I have, but haven't yet
committed (my fault).   I want to apply both of your fixes.  I'm attaching a
copy of his patch.

If you want to make me a very happy committer, you could apply his patch to
the current version under cvs, make your changes, and then produce a diff
from that (I'll then apply that and credit you both).

If you want to make me merely a fairly happy committer, you can say, "I'm
too busy to do that Dan, so I'm just running diff -u for my fixes based on
what's currently in cvs, and I'll send you that".  Then I can merge your and
Chris's work myself (which won't kill me, and will teach me to commit things
which are sent in!).

-Dan