costin 02/04/15 17:10:52
Modified: jk build.xml
Log:
Create a separate jar with the jni code.
The problem is that lib/container/tomcat-jk2 ( or server/lib/... ) will
end up in a deep class loader - and the JNI code will not be able to find
it ( without complex code to deal with class loaders in C ).
The solution is to put the jni code in the main loader ( but only the
jni code ).
We need to review it and make sure we don't mess with the security ( probably
we'll have to add some code to check the Priviledges of the caller ) - at
the moment the native interfaces are very experimental, after we get
everything functional most methods will be private and the access
controled much tightly.
Revision Changes Path
1.35 +5 -0 jakarta-tomcat-connectors/jk/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/build.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- build.xml 10 Apr 2002 03:21:42 -0000 1.34
+++ build.xml 16 Apr 2002 00:10:52 -0000 1.35
@@ -165,6 +165,11 @@
<exclude name="org/apache/jk/ant/**" />
</jar>
+ <jar jarfile="${jk.build}/lib/tomcat-jni.jar"
+ basedir="${jk.build}/classes" >
+ <include name="org/apache/jk/apr/**" />
+ </jar>
+
</target>
<target name="jkant" >
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
