"Christopher Schultz" <ch...@christopherschultz.net> wrote in message
news:4b9d8435.50...@christopherschultz.net...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Todd,
On 3/14/2010 1:41 PM, Todd Hicks wrote:
This may be a question better suited for the dev list, but I thought I'd
try
here first.
I've been troubleshooting a problem in one of my installations and was
reviewing the documentation here:
http://www.docjar.com/docs/api/org/apache/jk/config/ApacheConfig.html
(the
auto-config listener class) when it caught my attention that the path to
the
Apache mod_jk plugin file defaults to "modules/mod_jk.dll" on windows (if
the modJk option isn't set), yet the Apache connector for windows is
distributed as mod_jk-1.2.30-httpd-2.2.3.so (to be renamed to mod_jk.so).
Is
this just legacy and needs to be updated or am I missing something?
Should I
report this as a bug?
The real bug is that the ApacheConfig class still hasn't been put out of
its misery. Basically, nobody should ever use the ApacheConfig class
because it re-writes your mod_jk.conf file every time Tomcat starts.
This class has been removed from TC 7. And yes, is only somewhat works with
the retired httpd 1.3.x version, so nobody should ever use it.
You're better off reading the documentation for mod_jk and building your
own configuration file. It's not hard to set up a mapping for simple
things like *.jsp -> Tomcat and stuff like that. Once you've got the
simple stuff working, extending your configuration to include more
exotic options is still very easy.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkudhDUACgkQ9CaO5/Lv0PBUAQCfU6a4LrhrAZORb7zbzVIXRjOc
msUAniENxyXg+emGX9Ha3JmeKJSjNFWl
=uBUr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
