Howdy,
I think a jk2 release (v1.2.5 I believe) is very close, and has this bug
fixed. Check the recent jk2 release thread on tomcat-dev archives for
more information.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jon Skeet [mailto:[EMAIL PROTECTED]
Sent: Wednesday,
I think a jk2 release (v1.2.5 I believe) is very close, and
has this bug fixed.
That's excellent news. When it's released, will I be able to just dump a new
tomcat-jk2.jar in server/lib, and everything should spring to life, or is there more
to it than that?
Check the recent jk2 release
Howdy,
That's excellent news. When it's released, will I be able to just dump
a
new tomcat-jk2.jar in server/lib, and everything should spring to life,
or
is there more to it than that?
I don't know -- I don't use any of these connectors...
Check the recent jk2 release thread on tomcat-dev
Jon Skeet wrote:
I think a jk2 release (v1.2.5 I believe) is very close, and
has this bug fixed.
That's excellent news. When it's released, will I be able to just dump a new tomcat-jk2.jar in server/lib, and everything should spring to life, or is there more to it than that?
The release
The release that Yoav is referencing is a new mod_jk, which
is an Apache DSO module, not a JAR file. So yes, I guess you will be able
to sub in the new DSO as soon as you can build one or find a binary, but don't
confuse it with a JAR file.
In that case I can't see how it's going to help
I defer to Yoav, as it is entirely possible (though not probable) that I
am on crack. But the thread referenced is most definitely talking about
mod_jk.
John
Jon Skeet wrote:
The release that Yoav is referencing is a new mod_jk, which
is an Apache DSO module, not a JAR file. So yes, I
