>My idea is to build one connector per call of configure/make,
>--with-java should
>build the JNI support, correct?
>I have noted that common contains jk_jni_worker.c, should not
>we move it in jni?
no, jk_jni_worker could also be used into apache 1.3/2.0.
And that's HOW IBM use mod_jk on at least AS/400 using JNI
instead of AJP12/AJP13...
>> Many users asked about statically compiling mod_jk in Apache,
>> could you add a --with-apache flag ?
>
>Yes, but we cannot use apxs for that... Following the ideas of
>mod_webapp we
>should libtool for this purpose.
>Then it is more easy to use libtool for everything.
apxs is for DSO but the question was how to be sure the
mod_jk stuff could be compiled statically in apache ?
>>
>> Do you think we could add also the config dir path to have
>> default mod_jk.conf and workers.properties installed ?
>>
>> feature which could be added, is the config
>>
>> ie: --sysconfdir=/etc/httpd/conf (à la Redhat)
>
>If we use --with-apxs the conf is given by apxs, in case we
>use --with-apache
>yes.
>This means we need to support "make install".
PS: I commited your Makefile and configure stuff !!!