Yes I agree but in this situation, the file mod_jk-3.3-ap20.so is specifically stated on the Jakarta site as being for Apache 2.0. Thanks
-----Original Message----- From: Paul D. Bain [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 06, 2002 11:06 PM To: Tomcat Users List Subject: Re: Apache 2.0.35 + mod_jk-3.3-ap20.so At Saturday 4/6/02 10:43 PM, you wrote: >Hi I got all excited when I got the announcement that Apache 2.0.35 was no >longer a beta and was an official release so I downloaded the archive >"httpd-2.0.35.tar.gz" and installed it. I have only one hangup as of right >now and that's the inability to make use of the mod_jk connector. I am >currently getting the error from apache >"httpd: module "mod_jk.c" is not compatible with this version of Apache. >Please contact the vendor for the correct version." > >I am using the exact same configuration as with my old 1.3.24 apache. With >the exception of using the mod_jk-3.3-ap20.so module. It sounds as if I >would have to somehow know how to change the source code of this module to >account for the differences between whatever version of Apache 2.0 this was >compiled for and re-compile but frankly I haven't a clue where to start. Donald, That's exactly correct. Modules written for Apache 1.3 will _not_ work with Apache 2.0 unless they are re-written in order to be specific to 2.0. You should probably stick with 1.3. -- Paul Bain -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
