Chris, I'm good with writing my own configs. That's what I do for all of my installations (and probably where this one will end up). The reason I brought it up is because I am exploring Xampp for a client as a portable dev platform, and it's configured to use the ApacheConfig class out of the box. I'm sure it's done that way to reduce obstacles to entry for the newbie. But if it doesn't work as it should, the obstacle remains (at least for the Xampp novitiates). So are you saying then that the class isn't likely to be updated? Even if I submit it as a bug? I've already downloaded the source to try the fix.
-----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Sunday, March 14, 2010 8:50 PM To: Tomcat Users List Subject: Re: org.apache.jk.config.ApacheConfig modJk -----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. 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
