Not sure what JK2 needs to work, I don't use it. You should be able to build it from the same source package as JK. I was able to do so on my Red Hat test box, but it took quite a bit of hacking around.
JK isn't really "deprecated", the dev team is just pursuing JK2. In my opinion, JK is quite stable and JK2 is not ready for "prime time", though that is my personal preference. John > -----Original Message----- > From: Rasputin [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 16, 2002 8:40 AM > To: Tomcat Users List > Subject: Re: Apache-Tomcat HOWTO > > > * Turner, John <[EMAIL PROTECTED]> [1214 14:14]: > > > NOTE: the ./configure method assumes you have a sane build > environment: > > libtool, GNU make, autoconf, m4 > > > > a) cd to CONNECTOR_HOME/jk/native. > > > > b) check README and README.configure. > > > > c) run buildconf.sh: ./buildconf.sh. This will create a file called > > "configure" in CONNECTOR_HOME/jk/native. > > > > d) run configure: ./configure > --with-apxs=/some/path/to/apache/bin/apxs > > --with-java-home=${JAVA_HOME} > > > > e) run make: make > > I got this far from CVS, then had to manually copy mod_jk.so from > ./.libs/ in that directory into place for Apache2 to load it. > It seems fairly happy though, so that's not a problem. > > But unless I'm mistaken, this is a mod_jk connector. > I was hoping for JK2 (since I see warnings that JK is deprecated) - > I was following the docs linked from the 4.1 connector reference, are > they for Jk (rather than jk2)? > > I tried to build from the native2 directory, but this seems > to require a > local JDK - that's no go for me, NetBSD on sparc doesn't have > a 1.2 JVM :( > > Am I missing something, or does JK2 need a local JVM to work? > If so, why? > > -- > Rasputin :: Jack of All Trades - Master of Nuns > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
