cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/apr AprImpl.java
mturk 2002/09/18 23:26:17
Modified:jk/java/org/apache/jk/apr AprImpl.java
Log:
Add LogFactory to the class. This will prevent starting in case of error
in the classloader code.
Revision ChangesPath
1.26 +3 -0 jakarta-tomcat-connectors/jk/java/org/apache/jk/apr/AprImpl.java
Index: AprImpl.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/apr/AprImpl.java,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- AprImpl.java 14 Jul 2002 13:30:04 - 1.25
+++ AprImpl.java 19 Sep 2002 06:26:17 - 1.26
@@ -244,6 +244,7 @@
initialize();
jkSetAttribute(0, 0, channel:jni, starting);
+log.info(JK2: Initialized apr );
} catch( Throwable t ) {
throw new IOException( t.getMessage() );
}
@@ -336,4 +337,6 @@
ex.printStackTrace();
}
}
+private static org.apache.commons.logging.Log log=
+org.apache.commons.logging.LogFactory.getLog( AprImpl.class );
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common ChannelJni.java
mturk 2002/09/18 23:26:52
Modified:jk/java/org/apache/jk/common ChannelJni.java
Log:
Add the INFO log message when the channel is initialized.
Revision ChangesPath
1.14 +3 -1
jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ChannelJni.java
Index: ChannelJni.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/common/ChannelJni.java,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- ChannelJni.java 11 Jun 2002 00:11:03 - 1.13
+++ ChannelJni.java 19 Sep 2002 06:26:52 - 1.14
@@ -91,7 +91,9 @@
if( apr==null ) return;
// We'll be called from C. This deals with that.
-apr.addJkHandler( channelJni, this );
+apr.addJkHandler( channelJni, this );
+log.info(JK2: listening on channel.jni:jni );
+
if( next==null ) {
if( nextName!=null )
setNext( wEnv.getHandler( nextName ) );
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeansMBeanFactory.java
Amy Roh wrote: MBeanFactory.createStandardContext() still throws java.lang.IllegalArgumentException: Document base .\webapps\newpath does not exist or is not a readable directory after recent change in StandardContext. Is there something else missing that is preventing host.addChild(newContext) to work? I do not understand the problem, or what is wrong. BTW, before the change, the context was never properly initialized. The contexts which are in the host appbase will be automatically deployed, so I barely see a use case for that. This is working fine for me in all useful cases, so I will not fix it. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/conf workers2.properties
mturk 2002/09/18 23:28:24
Modified:jk/conf workers2.properties
Log:
Add the commons-logging.jar to the classpath. This is temporary workaround
to enable channelJni until the classloader code gets fixed.
Revision ChangesPath
1.16 +1 -1 jakarta-tomcat-connectors/jk/conf/workers2.properties
Index: workers2.properties
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/conf/workers2.properties,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- workers2.properties 11 Jul 2002 11:40:48 - 1.15
+++ workers2.properties 19 Sep 2002 06:28:24 - 1.16
@@ -68,7 +68,7 @@
[vm:]
info=Parameters used to load a JVM in the server process
#JVM=C:\jdk\jre\bin\hotspot\jvm.dll
-OPT=-Djava.class.path=${TOMCAT_HOME}/lib/tomcat-jni.jar;${TOMCAT_HOME}/lib/tomcat.jar
+OPT=-Djava.class.path=${TOMCAT_HOME}/lib/tomcat-jni.jar;${TOMCAT_HOME}/server/lib/commons-logging.jar
OPT=-Dtomcat.home=${TOMCAT_HOME}
OPT=-Dcatalina.home=${TOMCAT_HOME}
OPT=-Xmx128M
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11Http11Processor.java
Bill Barker wrote: - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 9:44 AM Subject: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java bobh2002/09/18 09:44:35 Modified:.gump.xml coyote/src/java/org/apache/coyote Request.java http11/src/java/org/apache/coyote/http11 Http11Processor.java Log: - This associates the socket with the Request. This is so the CertificatesValve.verify() can tell where (which socket) the Request is comeing from. Without this association, CertificatesValve.verify() returns with no SSL Handshake. - this change is in part based on feed back from; Vivek N. Yingxian Wang (JSSE), Craig M., Qingqing Ouyang I'm -1 on this, since having a socket in the Request makes no sense for Jk2. CertificatesValve is only for use with the deprecated HttpConnector. With Coyote, the SSL handling has moved to the connector (where it belonged in the first place). I agree. I forgot this was done through a notification, and 99% of the code was already there. Thanks for adding the clientauth support and removing the need for hacks. I will revert the changes to Http11Processor and Request. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12792] - login.jsp of admin webapp won't compile when tomcat is run as NT Service from D drive
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12792. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12792 login.jsp of admin webapp won't compile when tomcat is run as NT Service from D drive [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 06:35 --- *** This bug has been marked as a duplicate of 12387 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12387] - JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12387. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12387 JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 06:35 --- *** Bug 12792 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Fw: [BUG] jk2 jni doesn't work
Erm, somehow the reply-to didn't take.
- Original Message -
From: Bill Barker [EMAIL PROTECTED]
To: Mladen Turk [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 11:08 PM
Subject: Re: [BUG] jk2 jni doesn't work
- Original Message -
From: Mladen Turk [EMAIL PROTECTED]
To: 'Tomcat Developers List' [EMAIL PROTECTED]
Cc: Bill Barker [EMAIL PROTECTED]
Sent: Wednesday, September 18, 2002 10:43 PM
Subject: RE: [BUG] jk2 jni doesn't work
This is the classloader problem.
Think that Bill Baker is solving this, but until then add the
commons-logging.jar to the loaded classes when started inprocess:
OPT=-Djava.class.path=${TOMCAT_HOME}\bin\tomcat-jni.jar;${TOMCAT_HOME}\s
erver\lib\commons-logging.jar
Adding commons-logging to the classpath solves the JNI problem.
Bill, when can ve expect this will get solved?
Urm, it's really a separate issue. Last week I converted some of the 3.3
classes to using c-l, but trusted too much that if it compiles, then it
will
run. Since tonight I wanted to focus on the JSSE client-cert problem, I
just patched the startup scripts so that the 3.3.2-dev nightly would still
work.
However, I have no problem taking a look at the Jk2 ClassLoader issue at
the
same time that I try to work out why 3.3.2-dev broke.
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
at org.apache.jk.apr.AprImpl.clinit(AprImpl.java:348)
java.lang.NoClassDefFoundError
MT.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java
remm2002/09/18 23:40:49
Modified:http11/src/java/org/apache/coyote/http11
Http11Processor.java
Log:
- Revert patch.
Revision ChangesPath
1.36 +1 -3
jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java
Index: Http11Processor.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11/Http11Processor.java,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- Http11Processor.java 18 Sep 2002 16:44:35 - 1.35
+++ Http11Processor.java 19 Sep 2002 06:40:49 - 1.36
@@ -602,10 +602,8 @@
http11 = true;
http09 = false;
contentDelimitation = false;
-if (sslSupport != null) {
+if (sslSupport != null)
request.scheme().setString(https);
-request.setSocket( socket );
-}
MessageBytes protocolMB = request.protocol();
if (protocolMB.equals(Constants.HTTP_11)) {
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12795] - activation.jar in common/lib gives javax/activation/DataSource errors
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12795. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12795 activation.jar in common/lib gives javax/activation/DataSource errors --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 06:42 --- There should be no difference in behavior between 4.1 and 4.0 regarding activation.jar. If you have insights on what should be done to avoid the problem, please let me know. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote Request.java
remm2002/09/18 23:39:43
Modified:coyote/src/java/org/apache/coyote Request.java
Log:
- Revert patch.
Revision ChangesPath
1.15 +0 -16
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Request.java
Index: Request.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/Request.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- Request.java 18 Sep 2002 16:44:35 - 1.14
+++ Request.java 19 Sep 2002 06:39:43 - 1.15
@@ -73,8 +73,6 @@
import org.apache.tomcat.util.http.ContentType;
import org.apache.tomcat.util.http.Cookies;
-import java.net.Socket;
-
/**
* This is a low-level, efficient representation of a server request. Most
* fields are GC-free, expensive operations are delayed until the user code
@@ -186,9 +184,6 @@
private Response response;
private ActionHook hook;
-
-private Socket socket;
-
// - Properties
@@ -208,21 +203,10 @@
return headers;
}
-/* Used to associate this Request with a socket. Used later to do
- SSL related stuff. */
-public Socket getSocket() {
-return this.socket;
-}
-
-public void setSocket(Socket socket) {
-this.socket = socket;
-}
-
public UDecoder getURLDecoder() {
return urlDecoder;
}
-
// Request data
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Bug in DateTool in tomcat connector util?
Just viewed DateTool in CVS. Yes, format also has
thread problem and need fix. But, has parse been
fixed? I didn't see any change about it in v1.7.
--- Bill Barker [EMAIL PROTECTED] wrote:
I just checked in a fix for the format side
(setting the Last-Modified
header). This one is much harder to hit, but that
doesn't mean that you
can't. The parse side (getting the
If-Modified-Since header) has been
fixed in the nightly for quite some time now.
- Original Message -
From: Hugh J. L. [EMAIL PROTECTED]
To: Tomcat Developers List
[EMAIL PROTECTED]
Sent: Tuesday, September 17, 2002 7:12 PM
Subject: Bug in DateTool in tomcat connector util?
Hi,
I found a bug (?) when i was testing tomcat3.3
using
MS web stress tool. I set up large amount of
concurrent requests for static files, each with
header
If-Modified-Since which is newer than actual
last-modified-time of those requested files. I
should
have got 304 response for ALL requests in this
case,
however, i got many 304, a few 200, and even
NumberFormatException occasionally. This didn't
happen
if i tested using only one client thread. I looked
into java.text.SimpleDateFormat and suspected it
was
possibly a synchronization problem. Then I added
synchronization control to DateTool.parse(String,
DateFormat[]) as below and the problem was solved:
synchronized(format[i]) {
date = format[i].parse(dateString);
}
__
Do you Yahoo!?
New DSL Internet Access from SBC Yahoo!
http://sbc.yahoo.com
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11Http11Processor.java
Bob Herrmann wrote: On Wed, 2002-09-18 at 13:58, Remy Maucherat wrote: Remy Maucherat wrote: [EMAIL PROTECTED] wrote: bobh2002/09/18 09:44:35 Modified:.gump.xml coyote/src/java/org/apache/coyote Request.java http11/src/java/org/apache/coyote/http11 Http11Processor.java Log: - This associates the socket with the Request. This is so the CertificatesValve.verify() can tell where (which socket) the Request is comeing from. Without this association, CertificatesValve.verify() returns with no SSL Handshake. - this change is in part based on feed back from; Vivek N. Yingxian Wang (JSSE), Craig M., Qingqing Ouyang -1 (ie, revert this). The socket should already have been associated with the request, but as a note. It is available, and accessible. Ok, I checked it, and the socket os not currently associated with the request (I thought it was). OTOH, you shouldn't add a field for socket in the request (native webservers don't have the notion of a Java socket). Instead, use one of the notes. Ok, - change Http11Processor to use a note - change Request.java to it's original form - change the CertificatesValve.verify() Does that sound about right? For me: yes. Cheers, -bob Remy -- 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]
cvs commit: jakarta-tomcat/src/doc serverxml.html
hgomez 2002/09/19 00:57:07
Modified:src/doc serverxml.html
Log:
Add information about MXInterceptor
Revision ChangesPath
1.27 +62 -1 jakarta-tomcat/src/doc/serverxml.html
Index: serverxml.html
===
RCS file: /home/cvs/jakarta-tomcat/src/doc/serverxml.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- serverxml.html11 Sep 2002 17:35:26 - 1.26
+++ serverxml.html19 Sep 2002 07:57:06 - 1.27
@@ -228,6 +228,7 @@
lia href=#JservConfigJservConfig/a/li
lia href=#LoaderInterceptor11LoaderInterceptor11/a/li
lia href=#LogSetterLogSetter/a/li
+ lia href=#MXInterceptorMXInterceptor/a/li
lia href=#NSConfigNSConfig/a/li
lia href=#PolicyLoaderPolicyLoader/a/li
lia href=#TrustedLoaderTrustedLoader/a/li
@@ -2146,6 +2147,66 @@
lt;LogSetter name=quot;tc_logquot; verbosityLevel=quot;DEBUGquot; /gt;
lt;LogSetter name=quot;servlet_logquot; timestamps=quot;truequot;
verbosityLevel=quot;INFORMATIONquot;
path=quot;logs/servlet-${MMdd}.logquot; /gt;
+/pre
+
+hr size=5
+
+!-- --
+
+h3a name=MXInterceptorMXInterceptor/a/h3
+
+pbType:/b Configuration/p
+
+h4Description/h4
+
+pJMX MBeans support has been added to Tomcat 3.3.2, which allow you to manage
+Tomcat from any JMX console or via a simple browser by the build in HTTP Adaptor/p
+pTo enable JMX, you should add the lt;MxInterceptor /gt; in server.xml/p
+pTo also activate the HTTP Adaptor you should at least define the listen port/p
+
+h4Attributes/h4
+
+table border=1 cellpadding=2 cellspacing=0
+ tr valign=top
+thAttribute/th
+thDescription/th
+thDefault/th
+ /tr
+ tr valign=top
+tdport/td
+tdport where the JMX HTTP Adaptor will listen to, HTTP Adaptor will only be
loaded if the port is set/td
+td-1, no http adaptor loaded/td
+ /tr
+ tr valign=top
+tdhost/td
+tdhost/ip where the JMX HTTP Adaptor will listen to, only available when
using codeMX4J/code HTTP Adaptor/td
+tdnull/td
+ /tr
+ tr valign=top
+tdauthentication/td
+tdauthentication used by the JMX HTTP Adaptor, only available when using
codeMX4J/code HTTP Adaptor,
+it could be codenone/code, codebasic/code, codedigest/code/td
+tdnone/td
+ /tr
+ tr valign=top
+tduser/td
+tdthe user account which to be used with authentication/td
+tdnone, should be set to enable authentication/td
+ /tr
+ tr valign=top
+tdpassword/td
+tdthe password which to be used with authentication/td
+tdnone, should be set to enable authentication/td
+ /tr
+/table
+
+
+
+h4Example(s)/h4
+
+pre
+lt;MxInterceptor port=quot;8999quot; host=quot;mysystemquot;
authentication=quot;basicquot; user=quot;adminquot;
password=quot;changeillicoquot;/gt;
+lt;MxInterceptor /gt;
/pre
hr size=5
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/config MxInterceptor.java
hgomez 2002/09/19 00:58:07
Modified:src/share/org/apache/tomcat/modules/config
MxInterceptor.java
Log:
Add authentification method to MXInterceptor, need now to pass the
user/password to HTTP adaptor
Revision ChangesPath
1.4 +25 -2
jakarta-tomcat/src/share/org/apache/tomcat/modules/config/MxInterceptor.java
Index: MxInterceptor.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/config/MxInterceptor.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- MxInterceptor.java18 Sep 2002 07:57:09 - 1.3
+++ MxInterceptor.java19 Sep 2002 07:58:07 - 1.4
@@ -76,6 +76,9 @@
MBeanServer mserver;
private int port=-1;
private String host;
+private String auth;
+private String user;
+private String password;
// Tomcat callbacks
@@ -118,6 +121,23 @@
return host;
}
+public void setAuthentification( String auth ) {
+ if (none.equals(auth) || basic.equals(auth) || digest.equals(auth))
+ this.auth=auth;
+}
+
+public String getAuthentification() {
+return auth;
+}
+
+ public void setUser(String user) {
+ this.user = user;
+ }
+
+ public void setPassword(String password) {
+ this.password = password;
+ }
+
/* Start/stop */
ObjectName serverName=null;
@@ -133,7 +153,10 @@
mserver.setAttribute(serverName, new Attribute(Host, host));
mserver.setAttribute(serverName, new Attribute(Port, new
Integer(port)));
-
+
+if( auth!=null user!=null password!=null)
+mserver.setAttribute(serverName, new
Attribute(AuthenticationMethod, auth));
+
ObjectName processorName = new ObjectName(Http:name=XSLTProcessor);
mserver.createMBean(mx4j.adaptor.http.XSLTProcessor, processorName,
null);
mserver.setAttribute(serverName, new
Attribute(ProcessorName, processorName));
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/etc server.xml
hgomez 2002/09/19 01:02:27 Modified:src/etc server.xml Log: Add example MXInterceptor (still not enabled by default) Revision ChangesPath 1.98 +28 -0 jakarta-tomcat/src/etc/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat/src/etc/server.xml,v retrieving revision 1.97 retrieving revision 1.98 diff -u -r1.97 -r1.98 --- server.xml9 Apr 2002 19:43:27 - 1.97 +++ server.xml19 Sep 2002 08:02:27 - 1.98 @@ -69,6 +69,34 @@ Jdk12Interceptor / + !-- UnComment the following and comment out the +above to enable JMX monitoring. + +options are : + +port : http adaptor will listen to this port + +If you're using the MX4J HTTP Adaptor, you could also +set host and authentication : + +host : the MX4J http adaptor will listen to this IP/host + +authentication: the MX4J http adaptor will use HTTP authentification +method which could be (none, basic, digest) + +user: set the user to be entered when asking for user/password in + HTTP authentification. + +password : define the password for HTTP authentification + +Note, if you're using a JMX console, you don't have to +use the http adaptor + +MXInterceptor port=8999 authentification=basic + user=admin password=changeillico/ + + -- + !-- Non-standard invoker, for backward compat. ( /servlet/* ) -- InvokerInterceptor / -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [BUG] jk2 jni doesn't work
-Original Message-
From: jean-frederic clere
OPT=-Djava.class.path=${TOMCAT_HOME}\bin\tomcat-jni.jar;${TOMCAT_HOME}
\s
erver\lib\commons-logging.jar
I do not like this work-around: we will have end with a huge
classpath.
Neither do I, but this is the only way for now to be able to use the JNI
at all. If the JkMain or TomcatStarter loads the commons-logging at
first place we wouldn't have this problem.
I've added the LogFactory to the AprImpl that reports the error on TC
startup from inprocess and fails to start if the commons-logging is
missing, cause JNI wouldn't work properly at the first place without it.
So, fixing classloader is a showstopper on any jk2 release, and as I
said it is only a workaround that will disappear once that is fixed.
MT.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat build.xml
hgomez 2002/09/19 01:12:59
Modified:.build.xml
Log:
Majors modifications in build.xml :
- make it works from Eclipse IDE
- fix problems when building from non 'apache' layout (tc/jtc in same dir)
- add support for xerces2 parser or external parsers (usefull for
packagers like jpackage.org)
Revision ChangesPath
1.188 +145 -46 jakarta-tomcat/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat/build.xml,v
retrieving revision 1.187
retrieving revision 1.188
diff -u -r1.187 -r1.188
--- build.xml 11 Sep 2002 17:23:07 - 1.187
+++ build.xml 19 Sep 2002 08:12:59 - 1.188
@@ -28,8 +28,9 @@
--
property name=work.dir value=. /
- property name=tomcat.build value=${work.dir}/build/tomcat/
- property name=tomcat.dist value=${work.dir}/dist/tomcat/
+ !-- append basedir since jtc will need a full path for tomcat33.home --
+ property name=tomcat.build value=${basedir}/${work.dir}/build/tomcat/
+ property name=tomcat.dist value=${basedir}/${work.dir}/dist/tomcat/
!-- Location where various binaries are installed.
It can be c:\Program Files or /usr/share/java or
@@ -58,6 +59,9 @@
property name=ant.home location=${install.dir}/jakarta-ant/
property name=ant.bin location=${ant.home}/bin/
property name=ant.lib location=${ant.home}/lib/
+ property name=ant.jar location=${ant.home}/lib/ant.jar/
+ property name=optional.jar location=${ant.home}/lib/optional.jar/
+ property name=ant-optional.jar location=${ant.home}/lib/ant-optional.jar/
property name=jaxp.home location=bin /
@@ -96,6 +100,13 @@
property name=jtc.http11.lib location=${jtc.http11.home}/build/lib/
property name=jmx.jar location=${jakarta-tomcat-connectors}/lib/mx4j.jar/
+ property name=jmxtools.jar
location=${jakarta-tomcat-connectors}/lib/mx4j-tools.jar/
+
+ !-- xalan is required by MX4J HTTP adaptor --
+ property name=xalan.home location=${install.dir}/xalan/
+ property name=xalan.lib location=${xalan.home}/bin/
+ property name=xalan.jar location=${xalan.lib}/xalan.jar/
+ property name=xml-apis.jar location=${xalan.lib}/xml-apis.jar/
!-- Binaries checked in ( servlet.jar is not likely to change,
the 2.2 spec is final --
@@ -120,12 +131,28 @@
file=${jaxp.home}/jaxp.jar /
available property=jmx-present
file=${jmx.jar} /
+available property=jmxtools-present
+ file=${jmxtools.jar} /
+available property=xalan-present
+ file=${xalan.jar} /
available property=jaxp10-present
file=${jaxp.home}/parser.jar /
available property=jaxp11-present
file=${jaxp.home}/crimson.jar /
available property=xerces-present
file=${jaxp.home}/xerces.jar /
+condition property=xerces2-present
+ and
+available file=${xerces2.home}/xercesImpl.jar /
+available file=${xerces2.home}/xmlParserAPIs.jar /
+ /and
+/condition
+condition property=xml-parser-present
+ and
+available file=${xml-parser-impl.jar} /
+available file=${xml-parser-apis.jar} /
+ /and
+/condition
available property=jtc-present
file=${jakarta-tomcat-connectors} /
condition property=commons-dbcp.complete
@@ -135,6 +162,54 @@
available file=${commons-collections.jar} /
/and
/condition
+
+ !-- Some IDE like Eclipse didn't export ant and xml api --
+ !-- jars so javac will faild at compile time --
+ !-- To fix that, create some path ref which will be used --
+
+ path id=ant.class.path
+pathelement location=${ant.jar}//
+pathelement location=${optional.jar}/
+pathelement location=${ant-optional.jar}/
+ /path
+
+ path id=xml-apis.class.path
+pathelement location=${jaxp.home}/jaxp.jar/
+pathelement location=${xerces2.home}/xmlParserAPIs.jar/
+pathelement location=${xml-parser-apis.jar}/
+ /path
+
+ path id=tomcat_util.class.path
+pathelement location=${tomcat-util.jar}/
+ pathelement location=${commons-logging.jar} /
+ /path
+
+ path id=crypto.class.path
+pathelement location=${jcert.jar}/
+pathelement location=${jnet.jar}/
+pathelement location=${jsse.jar}/
+pathelement location=${puretls.jar}/
+ /path
+
+ path id=jdk.class.path
+fileset dir=${java.home}/..
+ include name=lib/tools.jar/
+/fileset
+fileset dir=${java.home}
+ include name=lib/classes.zip/
+/fileset
+ /path
+
+ path id=javadoc.classpath
+pathelement location=${servlet22.jar}/
+pathelement location=${jmx.jar}/
+path refid=ant.class.path/
+path
cvs commit: jakarta-tomcat-connectors/jk build.xml
hgomez 2002/09/19 01:19:01
Modified:jk build.xml
Log:
make it works from Eclipse IDE (which didn't export ant jars like
ant, ant-optional and xmls)
Revision ChangesPath
1.52 +15 -4 jakarta-tomcat-connectors/jk/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/build.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.xml 5 Sep 2002 15:08:36 - 1.51
+++ build.xml 19 Sep 2002 08:19:01 - 1.52
@@ -108,6 +108,13 @@
copy tofile=${jk.build}/lib/tomcat-coyote.jar
file=../coyote/build/lib/tomcat-coyote.jar /
+ !-- Fix build via ECLIPSE which didn't export ant's jars --
+path id=xml-apis.classpath
+ pathelement path=${jaxp.home}/jaxp.jar/
+ pathelement path=${xerces2.home}/xmlParserAPIs.jar/
+ pathelement path=${xml-parser-apis.jar}/
+/path
+
path id=build-main.classpath
fileset dir=../lib includes=*.jar /
pathelement location=../util/build/classes/
@@ -126,9 +133,9 @@
to nowhere, and tomcat_util will no longer be visible, nor
3.3 classes. --
pathelement
- location=${tomcat33.home}/lib/container/tomcat_util.jar/
- pathelement
- location=${tomcat33.home}/lib/common/servlet.jar/
+ location=${tomcat33.home}/lib/container/tomcat_util.jar/
+ pathelement
+location=${tomcat33.home}/lib/common/servlet.jar/
pathelement location=${coyote.home}/lib/tomcat-coyote.jar/
/path
@@ -161,7 +168,11 @@
unless=tomcat33.detect/
exclude name=org/apache/jk/common/JkMX.java unless=jmx.detect/
exclude name=org/apache/jk/common/Shm14.java unless=jdk14.detect/
- classpath refid=build-main.classpath/
+ classpath
+path refid=xml-apis.classpath/
+path refid=build-main.classpath/
+ /classpath
+
/javac
!-- Copy static resource files --
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/modules/config MxInterceptor.java
hgomez 2002/09/19 02:03:15
Modified:src/share/org/apache/tomcat/modules/config
MxInterceptor.java
Log:
Set the user/pwd for authentification
Revision ChangesPath
1.5 +7 -2
jakarta-tomcat/src/share/org/apache/tomcat/modules/config/MxInterceptor.java
Index: MxInterceptor.java
===
RCS file:
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/modules/config/MxInterceptor.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- MxInterceptor.java19 Sep 2002 07:58:07 - 1.4
+++ MxInterceptor.java19 Sep 2002 09:03:15 - 1.5
@@ -154,9 +154,14 @@
mserver.setAttribute(serverName, new Attribute(Port, new
Integer(port)));
+ // use authentication if user/password set
if( auth!=null user!=null password!=null)
mserver.setAttribute(serverName, new
Attribute(AuthenticationMethod, auth));
-
+
+ // add user names
+ mserver.invoke(serverName, addAuthorization, new Object[]
{user, password},
+new String[] {java.lang.String,
java.lang.String});
+
ObjectName processorName = new ObjectName(Http:name=XSLTProcessor);
mserver.createMBean(mx4j.adaptor.http.XSLTProcessor, processorName,
null);
mserver.setAttribute(serverName, new
Attribute(ProcessorName, processorName));
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [BUG] jk2 jni doesn't work
Mladen Turk wrote:
-Original Message-
From: jean-frederic clere
OPT=-Djava.class.path=${TOMCAT_HOME}\bin\tomcat-jni.jar;${TOMCAT_HOME}
\s
erver\lib\commons-logging.jar
I do not like this work-around: we will have end with a huge
classpath.
Neither do I, but this is the only way for now to be able to use the JNI
at all. If the JkMain or TomcatStarter loads the commons-logging at
first place we wouldn't have this problem.
I've added the LogFactory to the AprImpl that reports the error on TC
startup from inprocess and fails to start if the commons-logging is
missing, cause JNI wouldn't work properly at the first place without it.
So, fixing classloader is a showstopper on any jk2 release, and as I
said it is only a workaround that will disappear once that is fixed.
Adding a classloader that loads in ${TOMCAT_HOME}/bin is my idea but I need time
to do it (I am fighting with daemon in a BS2000).
MT.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: 4.1.10 tarball is borked.
On Wednesday, September 18, 2002, at 11:35 PM, Ian Darwin wrote: They admit that they aren't POSIX conformant, and claim that they will be, and will do it in a different way than GNUtar does at present. Do you know if this article is up to date? Well I guess it must be, it's on gnu.org. Obviously it would be good if all tars could read each others' archives. [pier@bubbles] ~ $ gnutar --help GNU `tar' saves many files together into a single tape or disk archive, and can restore individual files from the archive. [] Archive format selection: --posixwrite a POSIX conformant archive [...] GNU tar cannot read nor produce `--posix' archives. If POSIXLY_CORRECT is set in the environment, GNU extensions are disallowed with `--posix'. Support for POSIX is only partially implemented, don't count on it yet. [...] [pier@bubbles] ~ $ gnutar --version tar (GNU tar) 1.13 Copyright (C) 1988, 92,93,94,95,96,97,98, 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by John Gilmore and Jay Fenlason. [pier@bubbles] ~ $ Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: 4.1.10 tarball is borked.
[pier@bubbles] ~ $ gnutar --help GNU `tar' saves many files together into a single tape or disk archive, and can restore individual files from the archive. [] Archive format selection: --posixwrite a POSIX conformant archive [...] GNU tar cannot read nor produce `--posix' archives. If POSIXLY_CORRECT is set in the environment, GNU extensions are disallowed with `--posix'. Support for POSIX is only partially implemented, don't count on it yet. [...] [pier@bubbles] ~ $ gnutar --version tar (GNU tar) 1.13 Copyright (C) 1988, 92,93,94,95,96,97,98, 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Didn't gnutar is bundled with latest MacOS X ? tar is 1.13.19 on my Redhat 7.2, -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Jasper 2 Question
You can use some tea... http://opensource.go.com/ :-) Pier On Wednesday, September 18, 2002, at 10:33 PM, Lenny Karpel wrote: I use IntelliJ's IDEA product for Tomcat relared development .. I noted the following statement in thier bugs mailing list with regards to debugging JSP from thier IDE: As for Tomcat 4.1.x support, I'm afraid we are out-of-luck here. Tomcat 4.0.4 used to generate useful comments in the servlet code, that allowed the integration plugin to map jsp line numbers to servlet line numbers. But from the new version of Tomcat (Jasper2 in particular), this functionality is missing. At least I haven't been able to find anything to enable comment generation, and nobody from Tomcat user-list answered my question about this. Is this really true ?? Will this be fixed ?? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/doc serverxml.html
hgomez 2002/09/19 04:13:18 Modified:src/doc serverxml.html Log: typo, it's MxInterceptor and not MXInterceptor Revision ChangesPath 1.28 +4 -4 jakarta-tomcat/src/doc/serverxml.html Index: serverxml.html === RCS file: /home/cvs/jakarta-tomcat/src/doc/serverxml.html,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- serverxml.html19 Sep 2002 07:57:06 - 1.27 +++ serverxml.html19 Sep 2002 11:13:18 - 1.28 @@ -228,7 +228,7 @@ lia href=#JservConfigJservConfig/a/li lia href=#LoaderInterceptor11LoaderInterceptor11/a/li lia href=#LogSetterLogSetter/a/li - lia href=#MXInterceptorMXInterceptor/a/li + lia href=#MxInterceptorMxInterceptor/a/li lia href=#NSConfigNSConfig/a/li lia href=#PolicyLoaderPolicyLoader/a/li lia href=#TrustedLoaderTrustedLoader/a/li @@ -2153,7 +2153,7 @@ !-- -- -h3a name=MXInterceptorMXInterceptor/a/h3 +h3a name=MxInterceptorMxInterceptor/a/h3 pbType:/b Configuration/p @@ -2206,7 +2206,7 @@ pre lt;MxInterceptor port=quot;8999quot; host=quot;mysystemquot; authentication=quot;basicquot; user=quot;adminquot; password=quot;changeillicoquot;/gt; -lt;MxInterceptor /gt; +lt;erceptor /gt; /pre hr size=5 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat/src/etc server.xml
hgomez 2002/09/19 04:14:30 Modified:src/etc server.xml Log: typo, it's MxInterceptor and not MXInterceptor Revision ChangesPath 1.99 +2 -3 jakarta-tomcat/src/etc/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat/src/etc/server.xml,v retrieving revision 1.98 retrieving revision 1.99 diff -u -r1.98 -r1.99 --- server.xml19 Sep 2002 08:02:27 - 1.98 +++ server.xml19 Sep 2002 11:14:30 - 1.99 @@ -69,8 +69,7 @@ Jdk12Interceptor / - !-- UnComment the following and comment out the -above to enable JMX monitoring. + !-- Use MxInterceptor to enable JMX monitoring. options are : @@ -92,7 +91,7 @@ Note, if you're using a JMX console, you don't have to use the http adaptor -MXInterceptor port=8999 authentification=basic +MxInterceptor port=8999 authentification=basic user=admin password=changeillico/ -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk build.xml
hgomez 2002/09/19 04:18:30
Modified:jk build.xml
Log:
Update xml apis path refid
Revision ChangesPath
1.53 +1 -0 jakarta-tomcat-connectors/jk/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/build.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- build.xml 19 Sep 2002 08:19:01 - 1.52
+++ build.xml 19 Sep 2002 11:18:30 - 1.53
@@ -111,6 +111,7 @@
!-- Fix build via ECLIPSE which didn't export ant's jars --
path id=xml-apis.classpath
pathelement path=${jaxp.home}/jaxp.jar/
+ pathelement path=${jaxp.home}/crimson.jar/
pathelement path=${xerces2.home}/xmlParserAPIs.jar/
pathelement path=${xml-parser-apis.jar}/
/path
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Problem with Tomcat 3.3.2-dev and classloader for JMX
I've got a problem in loading MX4J and it's http adaptator. I initially put mx4j and mx4j-tools in lib/container, next to crimson and xalan but at init time the ClassLoader didn't find mx4j/mx4j-tools there. When I moved mx4j and mx4j-tools to lib/common, both are found but http connector couldn't be loaded since it need crimson and xalan which are in lib/container. How could I update MxInterceptor to make use of lib/container CL and sus being able to put mx4j jars in lib/container ??? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12810] New: - socket write error clicking between pages to fast
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810 socket write error clicking between pages to fast Summary: socket write error clicking between pages to fast Product: Tomcat 4 Version: 4.1.10 Platform: Other OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I get the following error when clicking between jsp pages before they load.. should I be getting these messages or is there a way to supress them. It does not seem right the clicking between pages before they fully load that I get these exceptions.. org.apache.jasper.JasperException: Connection reset by peer: socket write error at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:246) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationDispatcher.invoke (ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doForward (ApplicationDispatcher.java:432) at org.apache.catalina.core.ApplicationDispatcher.forward (ApplicationDispatcher.java:356) at com.controlj.green.web.servlets.NavigationMapperServlet.doGet (NavigationMapperServlet.java:154) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:471) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2397) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke (AccessLogValve.java:469) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnectio n(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt
DO NOT REPLY [Bug 12810] - socket write error clicking between pages to fast
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810 socket write error clicking between pages to fast [EMAIL PROTECTED] changed: What|Removed |Added Severity|Normal |Enhancement --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 12:07 --- Client disconnects are aparetly output. Ignore them. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/resources DONOTREMOVE
remm2002/09/19 05:40:49 Added: resources DONOTREMOVE Log: - Add a readme to hint that the temp dir shoudln't be removed. Revision ChangesPath 1.1 jakarta-tomcat-4.0/resources/DONOTREMOVE Index: DONOTREMOVE === Do not remove this directory -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 build.xml
remm2002/09/19 05:41:06
Modified:.build.xml
Log:
- Add a readme to hint that the temp dir shoudln't be removed.
Revision ChangesPath
1.74 +3 -0 jakarta-tomcat-4.0/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.xml,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -r1.73 -r1.74
--- build.xml 13 Jun 2002 00:21:36 - 1.73
+++ build.xml 19 Sep 2002 12:41:06 - 1.74
@@ -187,6 +187,9 @@
fileset dir=${tomcat.build}/webapps /
/copy
+!-- Copy temp file --
+copy todir=${tomcat.dist}/temp file=${basedir}/resources/DONOTREMOVE/
+
!-- Correct permissions and line endings on bin scripts --
fixcrlf srcdir=${tomcat.dist}/bin includes=*.sh eol=lf/
fixcrlf srcdir=${tomcat.dist}/bin includes=*.bat eol=crlf/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.1.txt
remm2002/09/19 06:17:17 Modified:.RELEASE-NOTES-4.1.txt Log: - Update release notes. Revision ChangesPath 1.20 +68 -1 jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt Index: RELEASE-NOTES-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.1.txt,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- RELEASE-NOTES-4.1.txt 5 Sep 2002 09:32:33 - 1.19 +++ RELEASE-NOTES-4.1.txt 19 Sep 2002 13:17:17 - 1.20 @@ -50,6 +50,12 @@ [4.1.10] Commons components: Upgrade to stable releases. +[4.1.11] Administration Webapp: + Add support for DefaultContext. + +[4.1.11] Documentation: + New JK and JK 2 documentation. + - Catalina New Features: @@ -168,6 +174,9 @@ [4.1.9] Administration Webapp: Specify charset in JSP pages. +[4.1.11] Administration Webapp: + Fix adding a context with the administration webapp. + -- Catalina Bug Fixes: @@ -395,6 +404,41 @@ [4.1.10] StandardContext: Add new swallowOutput flag, to allow configuring logger redirection. +[4.1.11] catalina.policy: + Modify the file to reflect the new URLs to be used for codebase + declarations. + +[4.1.11] StandardContext: + Change the timing of the directory context allocation (now done + during start which is more consistent with the lifecycle of other + components). + +[4.1.11] #12041 + CGIServlet: + Better fix for bugzilla 12041 running an extra thread to deal + with STDERR. + +[4.1.11] CGIServlet: + Fix for CGI scripts run from a POST operation never get any + posted data. + +[4.1.11] DefaultServlet: + Assume text file when MIME type is unknown for including purposes. + +[4.1.11] ManagerServlet: + Allow manager to do operations on the root webapp. + +[4.1.11] BootstrapService: + Allow parameters to BootstrapService for jni/mod_jk2. + +[4.1.11] FileDirContext: + Add an option to allow symlinking (allowLinking). + +[4.1.11] FileDirContext: + Make the case sensitivity check based on the value of the + caseSensitive flag rather than on the path separator. Most Unix OSes + can set that to false. + Jasper Bug Fixes: @@ -541,6 +585,29 @@ [4.1.10] #12128 Summary: JSP Comment end symbol not recognized in some cases + +[4.1.11] Compiler: + Update to work with Jikes with all features. + +[4.1.11] #12387 + Compiler: + Work around limitations of the Ant path tokenization by using files. + +[4.1.11] Generator: + For the conversion of the value used in includes and others + to a String, as was done in previous Tomcat releases. + +[4.1.11] Generator: + Added synchronization of NESTED and AT_BEGIN variables after call to + doStartTag() of tag handlers implementing IterationTag, but not + BodyTag. + +[4.1.11] #12432 + Generator: + Can't compile JSP with nested custom tags that have VariableInfo. + +[4.1.11] JspServletWrapper: + Fix Jasper when development option is set to false. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12815] New: - document.forms[0].submit() doesn't work with netscape 4.77
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12815. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12815 document.forms[0].submit() doesn't work with netscape 4.77 Summary: document.forms[0].submit() doesn't work with netscape 4.77 Product: Tomcat 4 Version: 4.1.10 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I've tried to submit a form using the method submit like the following: !-- a.jsp -- form action=b.jsp !-- -- a href=# onclick=document.forms[0].submit();test/a /form but it doesn't work. I've also tried with tomcat 3 and the first time i follow the link i got the message 2002-09-19 Ctx(): IOException in R(/) pipe broken ... The same with ie and nn on windows works both with windows and linux version of tomcat -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12810] - socket write error clicking between pages to fast
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12810 socket write error clicking between pages to fast --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 13:50 --- If someone can give me a starting point (as I am knee deep in the code now and have had no luck finding where this is getting handled) I will try and fix it, but I have had no luck yet.. ( I have been looking in the org.apache.coyote.http11.Http11Processor.process() and org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnectio n() methods.. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
sorry .. I don't understand your response ! are you saying that we shouldn't use jsp ? -Original Message- From: Pier Fumagalli [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:57 AM To: Tomcat Developers List Subject: Re: Jasper 2 Question You can use some tea... http://opensource.go.com/ :-) Pier On Wednesday, September 18, 2002, at 10:33 PM, Lenny Karpel wrote: I use IntelliJ's IDEA product for Tomcat relared development .. I noted the following statement in thier bugs mailing list with regards to debugging JSP from thier IDE: As for Tomcat 4.1.x support, I'm afraid we are out-of-luck here. Tomcat 4.0.4 used to generate useful comments in the servlet code, that allowed the integration plugin to map jsp line numbers to servlet line numbers. But from the new version of Tomcat (Jasper2 in particular), this functionality is missing. At least I haven't been able to find anything to enable comment generation, and nobody from Tomcat user-list answered my question about this. Is this really true ?? Will this be fixed ?? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/conf server.xml
bobh2002/09/19 09:37:36 Modified:catalina/src/conf server.xml Log: - jdk1.4 includes the JSSE package, update comment to reflect this Revision ChangesPath 1.6 +2 -2 jakarta-tomcat-catalina/catalina/src/conf/server.xml Index: server.xml === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/server.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- server.xml22 Aug 2002 12:48:56 - 1.5 +++ server.xml19 Sep 2002 16:37:36 - 1.6 @@ -66,8 +66,8 @@ entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): - * Download and install JSSE 1.0.2 or later, and put the JAR files - into $JAVA_HOME/jre/lib/ext. + * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or + later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Problem with Tomcat 3.3.2-dev and classloader for JMX
- Original Message - From: Henri Gomez [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 19, 2002 4:25 AM Subject: Problem with Tomcat 3.3.2-dev and classloader for JMX I've got a problem in loading MX4J and it's http adaptator. I initially put mx4j and mx4j-tools in lib/container, next to crimson and xalan but at init time the ClassLoader didn't find mx4j/mx4j-tools there. When I moved mx4j and mx4j-tools to lib/common, both are found but http connector couldn't be loaded since it need crimson and xalan which are in lib/container. How could I update MxInterceptor to make use of lib/container CL and sus being able to put mx4j jars in lib/container ??? What needs to happen is to split the j-t-c tomcat-util.jar into two jars (one for common and one for container/server). I haven't had the time to inventory what is there and decide what should go in which jar. Putting mx4j in common opens a major problem, since you make every webapp trusted that way. It's clear that o.a.t.u.mx needs to go in container. It's the rest I'm not sure of. -- 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]
Re: cvs commit:jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/netJSSESocketFactory.java
Humm... When I set SSL connector with clientAuth=true, Tomcat 5
gives me this,
Handshake failed javax.net.ssl.SSLHandshakeException:
javax.net.ssl.SSLProtocolException: handshake alert: no_certificate
On Thu, 2002-09-19 at 01:09, [EMAIL PROTECTED] wrote:
billbarker2002/09/18 22:09:28
Modified:util/java/org/apache/tomcat/util/net JSSESocketFactory.java
Log:
Fix problem with JSSE not honoring clientauth.
Now there should be now reason for anyone to believe that CertificatesValve should
be used ever with the CoyoteConnector. :-)
Revision ChangesPath
1.3 +16 -2
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/JSSESocketFactory.java
Index: JSSESocketFactory.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/JSSESocketFactory.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- JSSESocketFactory.java 18 Sep 2002 15:10:04 - 1.2
+++ JSSESocketFactory.java 19 Sep 2002 05:09:28 - 1.3
@@ -161,7 +161,18 @@
//determine whether we want client authentication
// the presence of the attribute enables client auth
- clientAuth = null != (String)attributes.get(clientauth);
+ String clientAuthStr=(String)attributes.get(clientauth);
+ if(clientAuthStr != null){
+ if(clientAuthStr.equals(true)){
+ clientAuth=true;
+ } else if(clientAuthStr.equals(false)) {
+ clientAuth=false;
+ } else {
+ throw new IOException(Invalid value ' +
+ clientAuthStr +
+ ' for 'clientauth' parameter:);
+ }
+ }
String keyPass=(String)attributes.get(keypass);
if( keyPass==null) keyPass=defaultKeyPass;
@@ -224,11 +235,14 @@
public Socket acceptSocket(ServerSocket socket)
throws IOException
{
+ SSLSocket asock = null;
try {
- return socket.accept();
+asock = (SSLSocket)socket.accept();
+asock.setNeedClientAuth(clientAuth);
} catch (SSLException e){
throw new SocketException(SSL handshake error + e.toString());
}
+ return asock;
}
/** Set server socket properties ( accepted cipher suites, etc)
--
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]
Re: Jasper 2 Question
on 2002/9/19 8:06 AM, Lenny Karpel [EMAIL PROTECTED] wrote: sorry .. I don't understand your response ! are you saying that we shouldn't use jsp ? I have been saying that for years now! http://jakarta.apache.org/velocity/ymtd/ymtd.html =) -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
Nooo. No more velocity.. Please.. No more.. -Original Message- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 1:48 PM To: tomcat-dev Subject: Re: Jasper 2 Question on 2002/9/19 8:06 AM, Lenny Karpel [EMAIL PROTECTED] wrote: sorry .. I don't understand your response ! are you saying that we shouldn't use jsp ? I have been saying that for years now! http://jakarta.apache.org/velocity/ymtd/ymtd.html =) -jon -- 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]
DO NOT REPLY [Bug 12824] New: - Tomcat is not able to find/compile jsp files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12824. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12824 Tomcat is not able to find/compile jsp files Summary: Tomcat is not able to find/compile jsp files Product: Tomcat 4 Version: 4.1.10 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Blocker Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have one other person that told me about the same problem and decided to stick with v4.04. This happens after installation when trying to run any web- app (admin or proprietary) except for ROOT. Check the stacktrace below: org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:477) at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:182) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:289) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:527) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2397) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex t(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnectio n(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt (PoolTcpEndpoint.java:508) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run (ThreadPool.java:533) at java.lang.Thread.run(Thread.java:536) root cause org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: 75 in the jsp file: /login.jsp Generated servlet error: [javac] Compiling 1 source file D:\Tomcat4.1\work\Standalone\localhost\admin\login_jsp.java:69: package org.apache.struts.taglib.html does not exist org.apache.struts.taglib.html.HtmlTag _jspx_th_html_html_0 = (org.apache.struts.taglib.html.HtmlTag) _jspx_tagPool_html_html_locale.get (org.apache.struts.taglib.html.HtmlTag.class); ^ An
DO NOT REPLY [Bug 12823] - SSL broke when clientAuth=true
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12823. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12823 SSL broke when clientAuth=true [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 18:28 --- Humm. I was a bit premature with this. My trust store wasn't even configured. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
is it right that when I ask a serious question about jasper2 that I get these totally ridiculous answers ? -Original Message- From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 11:48 AM To: tomcat-dev Subject: Re: Jasper 2 Question on 2002/9/19 8:06 AM, Lenny Karpel [EMAIL PROTECTED] wrote: sorry .. I don't understand your response ! are you saying that we shouldn't use jsp ? I have been saying that for years now! http://jakarta.apache.org/velocity/ymtd/ymtd.html =) -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
4.1.10: Bug in handling of custom valves?
I am not sure if this is more appropriate for the user list, I will rely on the new
moderator to redirect it as he sees fit (thank
you).
I am implementing a custom valve that adds some information to inbound requests. I've
noticed a strange behavior as follows:
Certain calls on the HttpServletRequest object seem to cause the request processing
chain to fail--the request is never delivered to
the appropriate servlet, and Tomcat returns a well-formatted, but blank, HTML page to
the client.
The following calls cause this behavior:
getServletPath()
getSession(boolean create)
getContextPath()
The following call _does_ not exhibit this behavior--the request is distributed
properly:
getRequestURL()
For example, the following code snippet causes the failure:
public void invoke(Request request, Response response, ValveContext context)
throws IOException, ServletException {
if (!(request instanceof HttpRequest) ||
!(response instanceof HttpResponse)) {
context.invokeNext(request, response);
return;
}
String reqPath=((HttpServletRequest) request.getRequest()).getServletPath();
if (reqPath.equals(/login)) {
// do nothing
context.invokeNext(request, response);
return;
}
// do actual work
context.invokeNext(request, response);
}
If I replace the call to getServletPath() with getRequestURL(), the request is
processed properly.
Is this a bug? Are their certain illegal calls on the request object that break the
valve chain?
My work around for now is to parse the requestURL myself rather than using the
convenience functions, but I can't find a work around
to not being able to access the Session.
Thanks in advance for any help.
- Jeff Wishnie
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: 4.1.10: Bug in handling of custom valves?
Custom valves are invoked before Catalina has mapped the request at whatever
level you put it at in your server.xml. This means that if you put it
inside of your Context declaration, then getContextPath should work, but
getServletPath won't. Placing it any higher up, then getContextPath won't
work.
Unless you *really* need access to Catalina internals, I'd strongly
recommend using a Filter instead of a Valve. They are functionally similar,
but you're state in a Filter is much easier to understand. Also, using a
Filter means that you are not tied to one particular version of Tomcat (or,
even to Tomcat at all :).
- Original Message -
From: Jeff Wishnie [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 19, 2002 11:35 AM
Subject: 4.1.10: Bug in handling of custom valves?
I am not sure if this is more appropriate for the user list, I will rely
on the new moderator to redirect it as he sees fit (thank
you).
I am implementing a custom valve that adds some information to inbound
requests. I've noticed a strange behavior as follows:
Certain calls on the HttpServletRequest object seem to cause the request
processing chain to fail--the request is never delivered to
the appropriate servlet, and Tomcat returns a well-formatted, but blank,
HTML page to the client.
The following calls cause this behavior:
getServletPath()
getSession(boolean create)
getContextPath()
The following call _does_ not exhibit this behavior--the request is
distributed properly:
getRequestURL()
For example, the following code snippet causes the failure:
public void invoke(Request request, Response response, ValveContext
context)
throws IOException, ServletException {
if (!(request instanceof HttpRequest) ||
!(response instanceof HttpResponse)) {
context.invokeNext(request, response);
return;
}
String reqPath=((HttpServletRequest)
request.getRequest()).getServletPath();
if (reqPath.equals(/login)) {
// do nothing
context.invokeNext(request, response);
return;
}
// do actual work
context.invokeNext(request, response);
}
If I replace the call to getServletPath() with getRequestURL(), the
request is processed properly.
Is this a bug? Are their certain illegal calls on the request object
that break the valve chain?
My work around for now is to parse the requestURL myself rather than using
the convenience functions, but I can't find a work around
to not being able to access the Session.
Thanks in advance for any help.
- Jeff Wishnie
[EMAIL PROTECTED]
--
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]
Re: cvs commit: jakarta-tomcat/src/etc server.xml
On Thu, 2002-09-19 at 21:14, [EMAIL PROTECTED] wrote: -MXInterceptor port=8999 authentification=basic +MxInterceptor port=8999 authentification=basic user=admin password=changeillico/ Shouldn't the above be authentication, not authentification? Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
On Fri, 2002-09-20 at 04:30, Lenny Karpel wrote: is it right that when I ask a serious question about jasper2 that I get these totally ridiculous answers ? Well, Jon and Pier are known to throw in a curly one from time to time, which keeps all of us here on the list in good spirits ;-) Anyway, there is a serious side to all this as JSP's are inherently evil. You'll find that creating true MVC applications in Velocity is almost trivial. I suggest you do read Jon's article. The fact that JSP's are official, doesn't mean they are good. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12725] - Jasper2 can't handle nested loops with jakarta UtilityTaglib
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12725. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12725 Jasper2 can't handle nested loops with jakarta UtilityTaglib --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 22:06 --- For what is worth, I've been able to see that it seems to be a bug with the jsp compiler, apparently it is adding an extra definition of the temporary variable at the top of the page, even when setting the pooling option off. I see a similar bug with a tag I wrote myself. Let me know if you need additional details ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
ok .. now I am really confused .. here is the tomcat development group .. the 'Official Reference Implementation' for JSP .. and I am being told by people within this group .. to NOT use it .. this is truly amazing .. how can this possibly be .. my original question is about 'bugs' in jasper2 .. not about what tools I should use .. my question is not one of religion .. once again .. the quote from the intellij site .. As for Tomcat 4.1.x support, I'm afraid we are out-of-luck here. Tomcat 4.0.4 used to generate useful comments in the servlet code, that allowed the integration plugin to map jsp line numbers to servlet line numbers. But from the new version of Tomcat (Jasper2 in particular), this functionality is missing. At least I haven't been able to find anything to enable comment generation, and nobody from Tomcat user-list answered my question about this. for myself .. all I want to know .. is if this 'situation' in jasper2 will be fixed .. if so .. when .. if not .. why .. we use JSP here .. as do quite a few others .. in quite a few places .. i did not post this question to find out that the developers of JSP (jasper) would rather I use something else .. could this possibly be how the 'managers' of this development effort feel ?? -Original Message- From: Bojan Smojver [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:25 PM To: Tomcat Dev List Subject: RE: Jasper 2 Question On Fri, 2002-09-20 at 04:30, Lenny Karpel wrote: is it right that when I ask a serious question about jasper2 that I get these totally ridiculous answers ? Well, Jon and Pier are known to throw in a curly one from time to time, which keeps all of us here on the list in good spirits ;-) Anyway, there is a serious side to all this as JSP's are inherently evil. You'll find that creating true MVC applications in Velocity is almost trivial. I suggest you do read Jon's article. The fact that JSP's are official, doesn't mean they are good. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12837] New: - Possible Memory Leak in I_R2.dll
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12837. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12837 Possible Memory Leak in I_R2.dll Summary: Possible Memory Leak in I_R2.dll Product: Tomcat 4 Version: 4.1.7 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Possible Memory Leak in I_R2.dll While doing some testing I noticed that the ISAPI connector using I_R2.dll appears that it may have a memory leak in it. Testing: All test were done using the ab.exe testing program Windows 2000 Server Service pack 2 Pentium 4, 1.5Ghz 512mb RAM Note: -c500 -n10 sugested by Nacho Test1: ab -c500 -n10 http://localhost/examples/jsp/index.html - start with a reboot to insure memory was cleared - Available memory at begining of test 364916K - inetinfo.exe process started out at 10,416K mem usage - Tomcat java.exe process started out at 19,440K mem usage - at 50,000 requests inetinfo was using 206,256K of memory the java process was hovering around 18,240K ab.exe its self was using 3,512K - at 70,000 requests NOTICE that the VIRTUAL SIZE is HUGE. The machine ran out of RAM CWD: C:\WINNT\system32\ CmdLine: C:\WINNT\System32\inetsrv\inetinfo.exe VirtualSize: 1137040 KB PeakVirtualSize: 1141200 KB WorkingSetSize: 14368 KBPeakWorkingSetSize:373076 KB NumberOfThreads: 91 CWD: D:\Tomcat 4.1\bin\ CmdLine: d:\j2sdk1.4.0.01\bin\java - Djava.endorsed.dirs=..\bin;..\comm on\endorsed -classpath d:\j2sdk1.4.0.01 \lib\tools.jar;..\bin\bootstrap.jar -D catalina.base=.. -Dcatalina.home=.. -Djava.io.tmpdir=..\temp org.apache.ca talina.startup.Bootstrap start VirtualSize: 217376 KB PeakVirtualSize: 217376 KB WorkingSetSize: 10232 KB PeakWorkingSetSize: 23420 KB NumberOfThreads: 90 ab.exe its self was using 3,512K - At end of RUN CWD: C:\WINNT\system32\ CmdLine: C:\WINNT\System32\inetsrv\inetinfo.exe VirtualSize: 1125764 KB PeakVirtualSize: 1141200 KB WorkingSetSize: 15068 KB PeakWorkingSetSize:373076 KB NumberOfThreads: 91 CWD: D:\Tomcat 4.1\bin\ CmdLine: d:\j2sdk1.4.0.01\bin\java - Djava.endorsed.dirs=..\bin;..\comm on\endorsed -classpath d:\j2sdk1.4.0.01 \lib\tools.jar;..\bin\bootstrap.jar -D catalina.base=.. -Dcatalina.home=.. -Djava.io.tmpdir=..\temp org.apache.ca talina.startup.Bootstrap start VirtualSize: 217376 KB PeakVirtualSize: 221536 KB WorkingSetSize: 10576 KB PeakWorkingSetSize: 23420 KB - overall system memory was at 3,896 free - after aborting the test at 50K request, the system did not free any of the memory from the inetinfo.exe process - tomcat was only using 10,416K during the same test - Right after starting the test the following error appeared in the TOMCAT console Sep 19, 2002 6:12:45 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite (SocketOutputStream.java:92) at java.net.SocketOutputStream.write (SocketOutputStream.java:126) at org.apache.jk.common.ChannelSocket.send (ChannelSocket.java:380) at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:558) at org.apache.jk.server.JkCoyoteHandler.action (JkCoyoteHandler.java:354) at org.apache.coyote.Response.action(Response.java:216) at org.apache.coyote.Response.finish(Response.java:336) at org.apache.coyote.tomcat4.CoyoteResponse.finishResponse(CoyoteRespons e.java:503) at org.apache.coyote.tomcat4.CoyoteAdapter.service (CoyoteAdapter.java:22 4) at org.apache.jk.server.JkCoyoteHandler.invoke (JkCoyoteHandler.java:256) at org.apache.jk.common.HandlerRequest.invoke (HandlerRequest.java:355) at org.apache.jk.common.ChannelSocket.invoke (ChannelSocket.java:563) at org.apache.jk.common.ChannelSocket.processConnection (ChannelSocket.ja va:535)
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session ManagerBase.java
amyroh 2002/09/19 15:55:48 Modified:catalina/src/share/org/apache/catalina DefaultContext.java Loader.java Manager.java catalina/src/share/org/apache/catalina/core StandardDefaultContext.java catalina/src/share/org/apache/catalina/loader WebappLoader.java catalina/src/share/org/apache/catalina/mbeans MBeanFactory.java MBeanUtils.java ServerLifecycleListener.java catalina/src/share/org/apache/catalina/session ManagerBase.java Log: Add Loader and Manager support in DefaultContext admin. Revision ChangesPath 1.5 +27 -10 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/DefaultContext.java Index: DefaultContext.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/DefaultContext.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- DefaultContext.java 9 Sep 2002 23:39:03 - 1.4 +++ DefaultContext.java 19 Sep 2002 22:55:47 - 1.5 @@ -64,6 +64,7 @@ package org.apache.catalina; +import java.beans.PropertyChangeListener; import javax.naming.directory.DirContext; import org.apache.catalina.deploy.ApplicationParameter; import org.apache.catalina.deploy.ContextEjb; @@ -205,6 +206,12 @@ public void setManager(Manager manager); +/** + * Return the naming resources associated with this web application. + */ +public NamingResources getNamingResources(); + + // -- Public Properties @@ -311,6 +318,14 @@ /** + * Add a property change listener to this component. + * + * @param listener The listener to add + */ +public void addPropertyChangeListener(PropertyChangeListener listener); + + +/** * Add a resource reference for this web application. * * @param resource New resource reference @@ -354,12 +369,6 @@ /** - * Return the naming resources associated with this web application. - */ -public NamingResources getNamingResources(); - - -/** * Return the set of application listener class names configured * for this application. */ @@ -550,6 +559,14 @@ * @param name Name of the parameter to remove */ public void removeParameter(String name); + + +/** + * Remove a property change listener from this component. + * + * @param listener The listener to remove + */ +public void removePropertyChangeListener(PropertyChangeListener listener); /** 1.6 +18 -4 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Loader.java Index: Loader.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Loader.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- Loader.java 22 Jul 2001 20:13:30 - 1.5 +++ Loader.java 19 Sep 2002 22:55:47 - 1.6 @@ -126,6 +126,20 @@ /** + * Return the DefaultContext with which this Manager is associated. + */ +public DefaultContext getDefaultContext(); + + +/** + * Set the DefaultContext with which this Manager is associated. + * + * @param defaultContext The newly associated DefaultContext + */ +public void setDefaultContext(DefaultContext defaultContext); + + +/** * Return the follow standard delegation model flag used to configure * our ClassLoader. */ 1.6 +19 -4 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Manager.java Index: Manager.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Manager.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- Manager.java 22 Jul 2001 20:13:30 - 1.5 +++ Manager.java 19 Sep 2002 22:55:47 - 1.6 @@ -110,6 +110,21 @@ /** + * Return the DefaultContext with which this Manager is associated. + */ +public DefaultContext getDefaultContext(); + + +/** + * Set the DefaultContext with which this Manager is associated. + * + * @param defaultContext The newly associated DefaultContext + */ +public void setDefaultContext(DefaultContext defaultContext); + + + +/** * Return the distributable flag for
cvs commit: jakarta-tomcat-4.0/webapps/admin/defaultcontext defaultcontext.jsp
amyroh 2002/09/19 15:56:05
Modified:webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext
AddDefaultContextAction.java
EditDefaultContextAction.java
SaveDefaultContextAction.java
webapps/admin/WEB-INF/classes/org/apache/webapp/admin/resources
DeleteDataSourcesAction.java
DeleteEnvEntriesAction.java
DeleteMailSessionsAction.java
DeleteResourceLinksAction.java ResourceUtils.java
SaveDataSourceAction.java SaveEnvEntryAction.java
SaveMailSessionAction.java
SaveResourceLinkAction.java
webapps/admin/defaultcontext defaultcontext.jsp
Log:
Add Loader and Manager support in DefaultContext admin.
Revision ChangesPath
1.2 +11 -11
jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext/AddDefaultContextAction.java
Index: AddDefaultContextAction.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext/AddDefaultContextAction.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- AddDefaultContextAction.java 11 Sep 2002 14:20:00 - 1.1
+++ AddDefaultContextAction.java 19 Sep 2002 22:56:05 - 1.2
@@ -155,14 +155,14 @@
defaultContextFm.setSwallowOutput(false);
defaultContextFm.setUseNaming(true);
//loader initialization
-//defaultContextFm.setLdrCheckInterval(15);
-//defaultContextFm.setLdrDebugLvl(0);
-//defaultContextFm.setLdrReloadable(false);
+defaultContextFm.setLdrCheckInterval(15);
+defaultContextFm.setLdrDebugLvl(0);
+defaultContextFm.setLdrReloadable(false);
//manager initialization
-//defaultContextFm.setMgrCheckInterval(60);
-//defaultContextFm.setMgrDebugLvl(0);
-//defaultContextFm.setMgrMaxSessions(-1);
-//defaultContextFm.setMgrSessionIDInit();
+defaultContextFm.setMgrCheckInterval(60);
+defaultContextFm.setMgrDebugLvl(0);
+defaultContextFm.setMgrMaxSessions(-1);
+defaultContextFm.setMgrSessionIDInit();
defaultContextFm.setDebugLvlVals(Lists.getDebugLevels());
defaultContextFm.setBooleanVals(Lists.getBooleanValues());
1.2 +67 -65
jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext/EditDefaultContextAction.java
Index: EditDefaultContextAction.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/webapps/admin/WEB-INF/classes/org/apache/webapp/admin/defaultcontext/EditDefaultContextAction.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- EditDefaultContextAction.java 11 Sep 2002 14:20:00 - 1.1
+++ EditDefaultContextAction.java 19 Sep 2002 22:56:05 - 1.2
@@ -151,9 +151,9 @@
// DefaultContext mBean
ObjectName cname = null;
// Loader mBean
-//ObjectName lname = null;
+ObjectName lname = null;
// Manager mBean
-//ObjectName mname = null;
+ObjectName mname = null;
StringBuffer sb = null;
try {
@@ -168,53 +168,55 @@
}
// Get the corresponding loader
-//try {
-//sb = new StringBuffer(cname.getDomain());
-//sb.append(:type=Loader);
-//sb.append(,path=);
-//sb.append(cname.getKeyProperty(path));
-//sb.append(,host=);
-//sb.append(cname.getKeyProperty(host));
-//sb.append(,service=);
-//sb.append(cname.getKeyProperty(service));
-//lname = new ObjectName(sb.toString());
-// } catch (Exception e) {
-//String message =
-//resources.getMessage(error.managerName.bad,
-// sb.toString());
-//getServlet().log(message);
-//response.sendError(HttpServletResponse.SC_BAD_REQUEST, message);
-//return (null);
-//}
+try {
+sb = new StringBuffer(cname.getDomain());
+sb.append(:type=DefaultLoader);
+String host = cname.getKeyProperty(host);
+if (host != null) {
+sb.append(,host=);
+sb.append(host);
+}
+sb.append(,service=);
+sb.append(cname.getKeyProperty(service));
+lname = new ObjectName(sb.toString());
+}
Re: Jasper 2 Question
Jasper2 is targeting JSR45, Debugging Support for Other Languages. On Thursday 19 September 2002 06:28 pm, Lenny Karpel wrote: ok .. now I am really confused .. here is the tomcat development group .. the 'Official Reference Implementation' for JSP .. and I am being told by people within this group .. to NOT use it .. this is truly amazing .. how can this possibly be .. my original question is about 'bugs' in jasper2 .. not about what tools I should use .. my question is not one of religion .. once again .. the quote from the intellij site .. As for Tomcat 4.1.x support, I'm afraid we are out-of-luck here. Tomcat 4.0.4 used to generate useful comments in the servlet code, that allowed the integration plugin to map jsp line numbers to servlet line numbers. But from the new version of Tomcat (Jasper2 in particular), this functionality is missing. At least I haven't been able to find anything to enable comment generation, and nobody from Tomcat user-list answered my question about this. for myself .. all I want to know .. is if this 'situation' in jasper2 will be fixed .. if so .. when .. if not .. why .. we use JSP here .. as do quite a few others .. in quite a few places .. i did not post this question to find out that the developers of JSP (jasper) would rather I use something else .. could this possibly be how the 'managers' of this development effort feel ?? -Original Message- From: Bojan Smojver [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 19, 2002 3:25 PM To: Tomcat Dev List Subject: RE: Jasper 2 Question On Fri, 2002-09-20 at 04:30, Lenny Karpel wrote: is it right that when I ask a serious question about jasper2 that I get these totally ridiculous answers ? Well, Jon and Pier are known to throw in a curly one from time to time, which keeps all of us here on the list in good spirits ;-) Anyway, there is a serious side to all this as JSP's are inherently evil. You'll find that creating true MVC applications in Velocity is almost trivial. I suggest you do read Jon's article. The fact that JSP's are official, doesn't mean they are good. Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Documenting the use of custom authenticators
Hi, I just spent several days grunging through code and running tests to figure out how to write and install a custom authenticator. And then Bill Barker dropped me an email and told me how in 2 sentences--thanks Bill! I think it would be helpful to better document the implementation and configuration of custom Valves and Authenticators. I'd be happy to either edit the existing docs or add a How-to if someone more experienced on this list will review what I write. Also, is there a process for submitting documentation changes? regards, Jeff Wishnie [EMAIL PROTECTED]
DO NOT REPLY [Bug 12718] - A variable scoped within a fragment in a tag file is always expsed as a string
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12718. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12718 A variable scoped within a fragment in a tag file is always expsed as a string [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-09-19 23:20 --- Fixed. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java JspUtil.java Validator.java
luehe 2002/09/19 16:21:40
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
JspUtil.java Validator.java
Log:
Fixed 12718: A variable scoped within a fragment in a tag file is
always expsed as a string
Revision ChangesPath
1.102 +67 -10
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java
Index: Generator.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- Generator.java13 Sep 2002 00:29:48 - 1.101
+++ Generator.java19 Sep 2002 23:21:39 - 1.102
@@ -587,7 +587,7 @@
JspUtil.FunctionSignature functionSignature =
new JspUtil.FunctionSignature( fnSignature,
-tli.getShortName(), err );
+tli.getShortName(), err, ctxt.getClassLoader() );
out.print( quote( functionSignature.getMethodName() ) );
out.print(, );
Class[] args = functionSignature.getParameterTypes();
@@ -701,6 +701,7 @@
private FragmentHelperClass fragmentHelperClass;
private int methodNesting;
private TagInfo tagInfo;
+ private ClassLoader loader;
/**
* Constructor.
@@ -709,11 +710,13 @@
ServletWriter out,
MethodsBuffer methodsBuffer,
FragmentHelperClass fragmentHelperClass,
+ClassLoader loader,
TagInfo tagInfo) {
this.isTagFile = isTagFile;
this.out = out;
this.methodsBuffer = methodsBuffer;
this.fragmentHelperClass = fragmentHelperClass;
+ this.loader = loader;
this.tagInfo = tagInfo;
methodNesting = 0;
handlerInfos = new Hashtable();
@@ -1831,21 +1834,66 @@
*/
class ParamVisitor extends Node.Visitor {
+ // The name of the fragment to which the jsp:param applies
+ private String fragName;
+
+ public ParamVisitor(String fragName) {
+ this.fragName = fragName;
+ }
+
public void visit(Node.ParamAction n) throws JasperException {
out.printin(_jspx_params.put();
out.print(quote(n.getTextAttribute(name)));
out.print(, );
out.print(attributeValue(n.getValue(), false,
- String.class, null));
+ getParamClass(n), null));
out.println(););
}
+
+ /*
+ * Checks to see if the given jsp:param matches a tag file
+ * variable scoped to the same fragment as the enclosing
+ * jsp:invoke. If a match is found, the class specified in
+ * the variable directive's 'variable-class' attribute (if
+ * present) is loaded and returned.
+ */
+ private Class getParamClass(Node.ParamAction n)
+ throws JasperException {
+
+ Class clazz = String.class;
+
+ TagVariableInfo[] tagVars = tagInfo.getTagVariableInfos();
+ if (tagVars != null) {
+ String paramName = n.getTextAttribute(name);
+ for (int i=0; itagVars.length; i++) {
+ String varName = tagVars[i].getNameGiven();
+ if (varName == null) {
+ // XXX name-from-attribute:
+ // What to do in this case?
+ }
+ String tagVarFrag = tagVars[i].getFragment();
+ if (!paramName.equals(varName)
+ || tagVarFrag == null
+ || !this.fragName.equals(tagVarFrag))
+ continue;
+ try {
+ clazz = JspUtil.toClass(tagVars[i].getClassName(),
loader);
+ } catch (ClassNotFoundException cnfe) {
+ throw new JasperException(cnfe);
+ }
+ }
+ }
+
+ return clazz;
+ }
}
// Assemble parameter map
out.printil(_jspx_params = new java.util.HashMap(););
if (n.getBody() != null) {
[PATCH] jakarta-servletapi-5::Another patch to the JSP XSD files
I just noticed my previous XSD patch from this Monday was never applied. Was there a problem? This patch contains diffs based on the current workspace state, not based on my previous patch. This patch contains another few patches to the XSD files. This affects both jsp_2_0.xsd and web-jsptaglibrary_2_0.xsd. Summary of changes: jsp_2_0.xsd: - Added id attributes to elements - Changed (description*, display-name*, icon*) to use common xsd:group reference for consistency. Definition is in common J2EE file. web-jsptaglibrary_2_0.xsd: - Added id attributes to elements - Changed (description*, display-name*, icon*) to use common xsd:group reference for consistency. Definition is in common J2EE file. - Escaped markup under xsd:documentation elements Files Modified: - jsr152/src/share/dtd/jsp_2_0.xsd - jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd - jsr154/src/share/dtd/jsp_2_0.xsd - jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd Please let me know if there are any questions or concerns. -- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] jakarta-servletapi-5::Another patch to the JSP XSD files
This time, with the patch. :) - Mark On Thu, 2002-09-19 at 19:36, Mark Roth wrote: I just noticed my previous XSD patch from this Monday was never applied. Was there a problem? This patch contains diffs based on the current workspace state, not based on my previous patch. This patch contains another few patches to the XSD files. This affects both jsp_2_0.xsd and web-jsptaglibrary_2_0.xsd. Summary of changes: jsp_2_0.xsd: - Added id attributes to elements - Changed (description*, display-name*, icon*) to use common xsd:group reference for consistency. Definition is in common J2EE file. web-jsptaglibrary_2_0.xsd: - Added id attributes to elements - Changed (description*, display-name*, icon*) to use common xsd:group reference for consistency. Definition is in common J2EE file. - Escaped markup under xsd:documentation elements Files Modified: - jsr152/src/share/dtd/jsp_2_0.xsd - jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd - jsr154/src/share/dtd/jsp_2_0.xsd - jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd Please let me know if there are any questions or concerns. -- Mark Roth, Java Software JSP 2.0 Co-Specification Lead Sun Microsystems, Inc. Index: jsr152/src/share/dtd/jsp_2_0.xsd === RCS file: /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/jsp_2_0.xsd,v retrieving revision 1.2 diff -u -r1.2 jsp_2_0.xsd --- jsr152/src/share/dtd/jsp_2_0.xsd 21 Aug 2002 16:17:48 - 1.2 +++ jsr152/src/share/dtd/jsp_2_0.xsd 19 Sep 2002 23:30:52 - @@ -8,7 +8,7 @@ version=2.0 xsd:annotation xsd:documentation -%W% %G% +@(#)jsp_2_0.xsds 1.12 09/18/02 /xsd:documentation /xsd:annotation @@ -105,12 +105,12 @@ minOccurs=0 maxOccurs=unbounded/ /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType !-- -- -xsd:simpleType name=jsp-fileType +xsd:complexType name=jsp-fileType xsd:annotation xsd:documentation @@ -120,9 +120,10 @@ /xsd:documentation /xsd:annotation -xsd:restriction base=j2ee:pathType/ - -/xsd:simpleType +xsd:simpleContent +xsd:restriction base=j2ee:pathType/ +/xsd:simpleContent +/xsd:complexType !-- -- @@ -145,12 +146,7 @@ /xsd:annotation xsd:sequence - xsd:element name=description - type=j2ee:descriptionType - minOccurs=0 maxOccurs=unbounded/ -xsd:element name=display-name - type=j2ee:display-nameType - minOccurs=0 maxOccurs=unbounded/ +xsd:group ref=j2ee:descriptionGroup/ xsd:element name=url-pattern type=j2ee:url-patternType maxOccurs=unbounded/ @@ -249,7 +245,7 @@ /xsd:annotation /xsd:element /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType !-- -- @@ -297,7 +293,7 @@ /xsd:element /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType /xsd:schema Index: jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd === RCS file: /home/cvspublic/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.2 diff -u -r1.2 web-jsptaglibrary_2_0.xsd --- jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 19 Aug 2002 16:29:49 - 1.2 +++ jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd 19 Sep 2002 23:30:52 - @@ -10,7 +10,7 @@ xsd:annotation xsd:documentation -@(#)web-jsptaglibrary_2_0.xsds 1.14 08/14/02 +@(#)web-jsptaglibrary_2_0.xsds 1.18 09/19/02 /xsd:documentation /xsd:annotation xsd:annotation @@ -61,12 +61,12 @@ and by indicating the version of the schema by using the version element as shown below: -taglib xmlns=http://java.sun.com/xml/ns/j2ee; +lt;taglib xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=... version=2.0 ... -/taglib +lt;/taglib The instance documents may indicate the published version of the schema using xsi:schemaLocation attribute @@ -137,7 +137,7 @@ !-- -- -xsd:simpleType name=body-contentType +xsd:complexType name=body-contentType xsd:annotation xsd:documentation @@ -163,17 +163,18 @@ /xsd:documentation /xsd:annotation -xsd:restriction base=j2ee:string -xsd:enumeration value=tagdependent/ -xsd:enumeration value=TAGDEPENDENT/ -xsd:enumeration value=JSP/ -xsd:enumeration value=empty/ -xsd:enumeration value=EMPTY/ -xsd:enumeration value=scriptless/ -xsd:enumeration value=SCRIPTLESS/ -/xsd:restriction - -/xsd:simpleType +
DO NOT REPLY [Bug 12839] New: - JSP with Bean site / context on anything other than C: will not work.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12839. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12839 JSP with Bean site / context on anything other than C: will not work. Summary: JSP with Bean site / context on anything other than C: will not work. Product: Tomcat 4 Version: 4.1.10 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] JSP compiler gives package not found error code for beans if the site context is set on for example D:\Test. It works just fine on C:\Test. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Jasper 2 Question
Quoting Lenny Karpel [EMAIL PROTECTED]: this is truly amazing .. how can this possibly be .. My apologies for making you upset :-( It honestly wasn't my intention. Jon helped me with my transition from JSP to Velocity and since then my web apps have become much simpler and easier to maintain. That was the point of my e-mail. As for Jasper, don't know, but I'm sure there will be people that do. Bojan - This mail sent through IMP: http://horde.org/imp/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime PageContextImpl.java
luehe 2002/09/19 17:45:26
Modified:jasper2/src/share/org/apache/jasper/runtime
PageContextImpl.java
Log:
Fixed 12638: ${pageContext.errorData.throwable.message} throws an error
Revision ChangesPath
1.20 +14 -6
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java
Index: PageContextImpl.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- PageContextImpl.java 29 Aug 2002 02:04:21 - 1.19
+++ PageContextImpl.java 20 Sep 2002 00:45:26 - 1.20
@@ -529,15 +529,23 @@
public void handlePageException(Throwable t)
throws IOException, ServletException
{
-// set the request attribute with the Throwable.
- request.setAttribute(javax.servlet.jsp.jspException, t);
-
if (errorPageURL != null !errorPageURL.equals()) {
+
+ // Set request attributes
+ request.setAttribute(javax.servlet.jsp.jspException, t);
+ request.setAttribute(javax.servlet.error.exception, t);
+ request.setAttribute(javax.servlet.error.status_code,
+ new Integer(HttpServletResponse.SC_INTERNAL_SERVER_ERROR));
+ request.setAttribute(javax.servlet.error.request_uri,
+ ((HttpServletRequest) request).getRequestURI());
+ request.setAttribute(javax.servlet.error.servlet_name,
+ config.getServletName());
try {
forward(errorPageURL);
} catch (IllegalStateException ise) {
include(errorPageURL);
}
+
} else {
// Otherwise throw the exception wrapped inside a ServletException.
// Set the exception as the root cause in the ServletException
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 12638] - ${pageContext.errorData.throwable.message} throws an error
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12638.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12638
${pageContext.errorData.throwable.message} throws an error
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||FIXED
--- Additional Comments From [EMAIL PROTECTED] 2002-09-20 00:47 ---
Fixed (pending patch to jsr152/src/share/javax/servlet/jsp/PageContext.java in
jakarta-servletapi-5 repository).
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/netJSSESocketFactory.java
Hi, Bill:
I have a question regarding your comment on the CertificatesValve should
not be used any more...
My understanding of how the CertificatesValve is used is following:
1. The clientAuth attribute in server.xml only determines whether
the Tomcat server by default will require client certificate
to authenticate (the default is false).
2. When a web app (servlet/jsp) that requires client auth
(auth-methodCLIENT-CERT/auth-method) is deployed in the Tomcat
server, Tomcat will install a CertificatesValve for the context
of this web app (regardless what Connector is used to process
https)
3. When a client opens a HttpsURLConnection to the protected web
resource, the CertificatesValve is invoked. And all it does is
to recognized that client auth is needed -- so it invalidates the
current socket session and forces a re-handshake with the client
-- hence the client authentication happens.
It seems to me that the JSSESocketFactory only takes care of the first
handshake. If Tomcat does not support a re-handshake, then how
can Tomcat dynamically discover that a client needs to send it's
certificate?
Can someone start the Tomcat server with clientAuth=false, but access
a URI that is protected by CLIENT-CERT? If yes, then I think a
re-handshake is a must.
Please lemme know if I am missing something here?
Thanx so much for your help!
Q^2
[EMAIL PROTECTED] wrote:
billbarker2002/09/18 22:09:28
Modified:util/java/org/apache/tomcat/util/net JSSESocketFactory.java
Log:
Fix problem with JSSE not honoring clientauth.
Now there should be now reason for anyone to believe that CertificatesValve should
be used ever with the CoyoteConnector. :-)
Revision ChangesPath
1.3 +16 -2
jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/JSSESocketFactory.java
Index: JSSESocketFactory.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/net/JSSESocketFactory.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- JSSESocketFactory.java 18 Sep 2002 15:10:04 - 1.2
+++ JSSESocketFactory.java 19 Sep 2002 05:09:28 - 1.3
@@ -161,7 +161,18 @@
//determine whether we want client authentication
// the presence of the attribute enables client auth
- clientAuth = null != (String)attributes.get(clientauth);
+ String clientAuthStr=(String)attributes.get(clientauth);
+ if(clientAuthStr != null){
+ if(clientAuthStr.equals(true)){
+ clientAuth=true;
+ } else if(clientAuthStr.equals(false)) {
+ clientAuth=false;
+ } else {
+ throw new IOException(Invalid value ' +
+ clientAuthStr +
+ ' for 'clientauth' parameter:);
+ }
+ }
String keyPass=(String)attributes.get(keypass);
if( keyPass==null) keyPass=defaultKeyPass;
@@ -224,11 +235,14 @@
public Socket acceptSocket(ServerSocket socket)
throws IOException
{
+ SSLSocket asock = null;
try {
- return socket.accept();
+asock = (SSLSocket)socket.accept();
+asock.setNeedClientAuth(clientAuth);
} catch (SSLException e){
throw new SocketException(SSL handshake error + e.toString());
}
+ return asock;
}
/** Set server socket properties ( accepted cipher suites, etc)
--
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]
cvs commit: jakarta-servletapi-5/jsr152/src/share/javax/servlet/jsp PageContext.java
patrickl2002/09/19 18:55:43
Modified:jsr152/src/share/javax/servlet/jsp PageContext.java
Log:
Fix for bug 12638
Submitted by: Jan Luehe ([EMAIL PROTECTED])
Revision ChangesPath
1.3 +4 -4
jakarta-servletapi-5/jsr152/src/share/javax/servlet/jsp/PageContext.java
Index: PageContext.java
===
RCS file:
/home/cvs/jakarta-servletapi-5/jsr152/src/share/javax/servlet/jsp/PageContext.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PageContext.java 19 Aug 2002 16:29:49 - 1.2
+++ PageContext.java 20 Sep 2002 01:55:43 - 1.3
@@ -567,11 +567,11 @@
*/
public ErrorData getErrorData() {
return new ErrorData(
- (Throwable)getAttribute( javax.servlet.error.exception ),
- ((Integer)getAttribute(
+ (Throwable)getRequest().getAttribute( javax.servlet.error.exception ),
+ ((Integer)getRequest().getAttribute(
javax.servlet.error.status_code )).intValue(),
- (String)getAttribute( javax.servlet.error.request_uri ),
- (String)getAttribute( javax.servlet.error.servlet_name ) );
+ (String)getRequest().getAttribute( javax.servlet.error.request_uri ),
+ (String)getRequest().getAttribute( javax.servlet.error.servlet_name ) );
}
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr154/src/share/dtd jsp_2_0.xsd web-jsptaglibrary_2_0.xsd
patrickl2002/09/19 18:56:44 Modified:jsr152/src/share/dtd jsp_2_0.xsd web-jsptaglibrary_2_0.xsd jsr154/src/share/dtd jsp_2_0.xsd web-jsptaglibrary_2_0.xsd Log: Updates to conform to current spec draft Submitted by: Mark Roth ([EMAIL PROTECTED]) Revision ChangesPath 1.3 +10 -14jakarta-servletapi-5/jsr152/src/share/dtd/jsp_2_0.xsd Index: jsp_2_0.xsd === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/src/share/dtd/jsp_2_0.xsd,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jsp_2_0.xsd 21 Aug 2002 16:17:48 - 1.2 +++ jsp_2_0.xsd 20 Sep 2002 01:56:44 - 1.3 @@ -8,7 +8,7 @@ version=2.0 xsd:annotation xsd:documentation -%W% %G% +@(#)jsp_2_0.xsds 1.12 09/18/02 /xsd:documentation /xsd:annotation @@ -105,12 +105,12 @@ minOccurs=0 maxOccurs=unbounded/ /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType !-- -- -xsd:simpleType name=jsp-fileType +xsd:complexType name=jsp-fileType xsd:annotation xsd:documentation @@ -120,9 +120,10 @@ /xsd:documentation /xsd:annotation -xsd:restriction base=j2ee:pathType/ - -/xsd:simpleType +xsd:simpleContent +xsd:restriction base=j2ee:pathType/ +/xsd:simpleContent +/xsd:complexType !-- -- @@ -145,12 +146,7 @@ /xsd:annotation xsd:sequence - xsd:element name=description - type=j2ee:descriptionType - minOccurs=0 maxOccurs=unbounded/ -xsd:element name=display-name - type=j2ee:display-nameType - minOccurs=0 maxOccurs=unbounded/ +xsd:group ref=j2ee:descriptionGroup/ xsd:element name=url-pattern type=j2ee:url-patternType maxOccurs=unbounded/ @@ -249,7 +245,7 @@ /xsd:annotation /xsd:element /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType !-- -- @@ -297,7 +293,7 @@ /xsd:element /xsd:sequence - +xsd:attribute name=id type=xsd:ID/ /xsd:complexType /xsd:schema 1.3 +71 -86 jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd Index: web-jsptaglibrary_2_0.xsd === RCS file: /home/cvs/jakarta-servletapi-5/jsr152/src/share/dtd/web-jsptaglibrary_2_0.xsd,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- web-jsptaglibrary_2_0.xsd 19 Aug 2002 16:29:49 - 1.2 +++ web-jsptaglibrary_2_0.xsd 20 Sep 2002 01:56:44 - 1.3 @@ -10,7 +10,7 @@ xsd:annotation xsd:documentation -@(#)web-jsptaglibrary_2_0.xsds 1.14 08/14/02 +@(#)web-jsptaglibrary_2_0.xsds 1.18 09/19/02 /xsd:documentation /xsd:annotation xsd:annotation @@ -61,12 +61,12 @@ and by indicating the version of the schema by using the version element as shown below: -taglib xmlns=http://java.sun.com/xml/ns/j2ee; +lt;taglib xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=... version=2.0 ... -/taglib +lt;/taglib The instance documents may indicate the published version of the schema using xsi:schemaLocation attribute @@ -137,7 +137,7 @@ !-- -- -xsd:simpleType name=body-contentType +xsd:complexType name=body-contentType xsd:annotation xsd:documentation @@ -163,17 +163,18 @@ /xsd:documentation /xsd:annotation -xsd:restriction base=j2ee:string -xsd:enumeration value=tagdependent/ -xsd:enumeration value=TAGDEPENDENT/ -xsd:enumeration value=JSP/ -xsd:enumeration value=empty/ -xsd:enumeration value=EMPTY/ -xsd:enumeration value=scriptless/ -xsd:enumeration value=SCRIPTLESS/ -/xsd:restriction - -/xsd:simpleType +xsd:simpleContent +xsd:restriction base=j2ee:string +xsd:enumeration value=tagdependent/ +xsd:enumeration value=TAGDEPENDENT/ +xsd:enumeration value=JSP/ +xsd:enumeration value=empty/ +xsd:enumeration value=EMPTY/ +xsd:enumeration value=scriptless/ +xsd:enumeration value=SCRIPTLESS/ +/xsd:restriction +/xsd:simpleContent +/xsd:complexType !--
Re: cvs commit: jakarta-tomcat/src/shell tomcat.bat tomcat.sh
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 9:21 PM Subject: cvs commit: jakarta-tomcat/src/shell tomcat.bat tomcat.sh billbarker2002/09/18 21:21:17 Modified:src/shell tomcat.bat tomcat.sh Log: Temporary stop-gap until I work out all of the ClassLoader issues. Ok, there are a couple of options here: 1) Add a Class-Path to the Manifest (and make a comment in the release notes for people using Java 1.1.x). 2) Revert o.a.t.u.compat.* and o.a.t.u.depend.* to using System.err instead of c-l, since they are loaded in the System ClassLoader when running from the scripts. 3) Re-implement the required methods from o.a.t.u.compat.* in o.a.t.startup.Main so that we can leave o.a.t.u.depend.* and o.a.t.u.compat.* out of the jar. My personal choices are in order, 3-1-2. However 1 is the easiest, and seems to be in the direction that the proposals are heading. Opinions (Larry/Costin)? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
