Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 54683 invoked from network); 10 May 2002 23:40:13 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 May 2002 23:40:13 -0000 Received: (qmail 2785 invoked by uid 97); 10 May 2002 23:40:13 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 2769 invoked by uid 97); 10 May 2002 23:40:12 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 2757 invoked by uid 98); 10 May 2002 23:40:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costinm owned process doing -bs Date: Fri, 10 May 2002 16:38:16 -0700 (PDT) From: X-X-Sender: To: Tomcat Developers List Subject: Re: [JK2] The IIS Connector is ( more or less ) working!! In-Reply-To: <80F5674514B4D311BAFC0040F6A45EEE2A85DB@ntserver> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sat, 11 May 2002, Ignacio J. Ortega wrote: > Costin, Can you summarize a bit, what i need to build and use to have > tc33 & tc40 working with JNI? Not much - you do need APR, you should use the version that is bundled with Apache2.0 ( the DLL and includes ). Then compile with HAVE_JNI enabled, check the config of [vm], [worker.jni] and [channel.jni]. The [vm] objects deals with loading the VM - it needs classpath and all the params. [worker.jni] will execute a class ( calling main() ), you can include as many as you want ( but of course you need TomcatStarter if you want to run a version of tomcat ). [channel.jni] will forward the requests. You'll probably need to fix AprImpl a bit, right now there is a mod_jk.so hardcoded and probably few other things need to change to get it to work on windows. If you can wait till next week, I can help with this part. One important piece ( not related directly with jni ) is the jk_shm object and Shm on java side. Those will play an important role, and we need to get them working on windows. Shm is not a big problem, if we get into problems we can use JDK1.4's nio - i.e. no JNI is needed. Costin -- To unsubscribe, e-mail: For additional commands, e-mail: