>
>javac --classpath /tomcat_path/.../catalina.jar *.java
>jar cf Ajp13.jar *.class
>
>>
>> any thoughts on the directory structure in jakarta-tomcat-connector?
>> i'm assuming there's going to be common ajpxx code, then
>> ajpxx-servletcontainer-connector code, then common util code (i.e.
>> MessageBytes, OutputBuffer), etc.. any ideas on how this will all be
>> segmented out?
>
>like jakarta-tomcat-connectors/mod_jk/java/org/apache.../ajp13/*.java
>jakarta-tomcat-connectors/mod_jk/java/org/apache.../ajpcommon/*.java
>jakarta-tomcat-connectors/mod_jk/java/org/apache.../connectors/*.java
>jakarta-tomcat-connectors/mod_jk/apache-1.3 for apache-1.3 and so on?
>
>
>Should we really use Ant? To build the C files on many
>platforms we will
>need configure, why not doing like JServ in the past? - A
>configure that
>asks or guesses the Webserver location, Tomcat location and java path -
The project will be in two parts, java and native.
I'd like to see ant used for the java part and
configure for the native.
native hackers know about configure and libtool.
java developpers start to learn using ant.
Just to help each community find its mark.
JF would you like doing the autoconf stuff for
the native part ?
The source is :
jakarta-tomcat-connectors/src/java/....
jakarta-tomcat-connectors/src/native/...
In my idea native is just mod_jtc, which replace mod_jk.
We have only connector projects here for now, mod_jtc (mod_jk)
