-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]]
Sent: 16. lipanj 2002 5:03
To: [EMAIL PROTECTED]
Subject: Re: TomcatMonitor
I wouldn't have a problem with that. No sense reinventing the wheel
for one or the other of us... +1.
and a ++1 here.
(longish, please read if you're familiar with Jasper sources)
I'm using Jasper which comes packaged with JBoss 3.0. One of the JSPs
has the following code:
BodyContent bc = pageContext.pushBody();
request.getRequestDispatcher(jspName).forward(request, response);
pageContext.popBody();
I think I'll be -0 on this.
There are 2 main reasons:
1. There are not too many people who work on the JNI - it's tricky
and not very easy, and for this reason we had quite a few improvements
in jk1. The performance of the old jni worker were pretty poor,
with many of the optimizations done in
On Sat, 15 Jun 2002, Mladen Turk wrote:
Hi,
As a maker of ApacheMonitor I _know_ that the support for the Tomcat's
start/stop/monitor would be trivial.
I can't wait to see it implemented...
Costin
The question is can we (Apache2 and Tomcat) agree to coexist, or make
two different try
jfclere 2002/06/16 11:13:52
Modified:jk/support jk_apxs.m4
Log:
libexec is the place where modules are, not the libraries.
Revision ChangesPath
1.3 +2 -2 jakarta-tomcat-connectors/jk/support/jk_apxs.m4
Index: jk_apxs.m4
