cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans MBeanUtils.java NamingResourcesMBean.java ServerLifecycleListener.java mbeans-descriptors.xml
amyroh 2002/06/12 00:39:24
Modified:catalina/src/share/org/apache/catalina/mbeans
MBeanUtils.java NamingResourcesMBean.java
ServerLifecycleListener.java mbeans-descriptors.xml
Log:
Add JNDI resources support for Context.
Revision ChangesPath
1.40 +84 -14
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java
Index: MBeanUtils.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/mbeans/MBeanUtils.java,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- MBeanUtils.java 9 Jun 2002 00:23:27 - 1.39
+++ MBeanUtils.java 12 Jun 2002 07:39:23 - 1.40
@@ -921,8 +921,25 @@
throws MalformedObjectNameException {
ObjectName name = null;
-name = new ObjectName(domain + :type=Environment,name= +
+Object container =
+environment.getNamingResources().getContainer();
+if (container instanceof Server) {
+name = new ObjectName(domain + :type=Environment,name= +
environment.getName());
+} else if (container instanceof Context) {
+String path = ((Context)container).getPath();
+if (path.length() 1)
+path = /;
+name = new ObjectName(domain + :type=Environment,name= +
+ environment.getName() + ,path= +
+ path);
+} else if (container instanceof DefaultContext) {
+String defaultContextName = ((DefaultContext)container).getName();
+name = new ObjectName(domain + :type=Environment,name= +
+ environment.getName() + ,defaultContext= +
+ defaultContextName);
+}
+
return (name);
}
@@ -943,9 +960,28 @@
ObjectName name = null;
String encodedResourceName = encodeStr(resource.getName());
-name = new ObjectName(domain + :type=Resource,class= +
+Object container =
+resource.getNamingResources().getContainer();
+if (container instanceof Server) {
+name = new ObjectName(domain + :type=Resource,class= +
resource.getType()+,name= +
encodedResourceName);
+} else if (container instanceof Context) {
+String path = ((Context)container).getPath();
+if (path.length() 1)
+path = /;
+name = new ObjectName(domain + :type=Resource,class= +
+ resource.getType()+,name= +
+ encodedResourceName + ,path= +
+ path);
+} else if (container instanceof DefaultContext) {
+String defaultContextName = ((DefaultContext)container).getName();
+name = new ObjectName(domain + :type=Resource,class= +
+ resource.getType()+,name= +
+ encodedResourceName + ,defaultContext= +
+ defaultContextName);
+}
+
return (name);
}
@@ -966,9 +1002,28 @@
ObjectName name = null;
String encodedResourceLinkName = encodeStr(resourceLink.getName());
-name = new ObjectName(domain + :type=ResourceLink,class= +
+Object container =
+resourceLink.getNamingResources().getContainer();
+if (container instanceof Server) {
+name = new ObjectName(domain + :type=ResourceLink,class= +
resourceLink.getType()+,name= +
encodedResourceLinkName);
+} else if (container instanceof Context) {
+String path = ((Context)container).getPath();
+if (path.length() 1)
+path = /;
+name = new ObjectName(domain + :type=ResourceLink,class= +
+ resourceLink.getType()+,name= +
+ encodedResourceLinkName + ,path= +
+ path);
+} else if (container instanceof DefaultContext) {
+String defaultContextName = ((DefaultContext)container).getName();
+name = new ObjectName(domain + :type=ResourceLink,class= +
+ resourceLink.getType()+,name= +
+ encodedResourceLinkName + ,defaultContext= +
+ defaultContextName);
+}
+
return (name);
}
@@ -1210,16 +1265,31 @@
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
[EMAIL PROTECTED] wrote: On Tue, 11 Jun 2002, Remy Maucherat wrote: I'll adopt a hard line stance, since I think it is the only way to avoid the situation with dependencies to get out of hand (where we bundle custom builds of every dependent module). We have to use only release components in a release build. If there are too many issues, then it is our fault for relying on broken components, and those dependencies must be removed. I agree that using only stable releases is the ideal solution. Except I don't think it scales. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. I don't agree, I'd like to use the latest stable version. I'd like that too. I just don't think it works. At least for jakarta components we should try to make it work. Well, let's close this issue - the release manager should do the build with whatever he likes, we vote on the end result. If you can get the stars to align on the release date and use only stable versions - great. There are 2 points: - Making reliable releases. - Having reproduceable build. I am going to update the build.xml to help for the second (as commons-logging 1.0.1 is still not released). I am also thinking that if the problem is in commons-logging we should help to make the needed release hapend. Costin -- 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: Tomcat performance article
I was wondering if anyone in the Tomcat group has read this document and what their opinion or official statement was. http://radio.weblogs.com/0107789/stories/2002/05/28/isTomcatCrap. html We are in the process of deploying our application and trying to determine the best servlet engine for our service. Hum, from what I could see the test are conducted with an old version of Tomcat 4.x (latest release is 4.0.3). To be released 4.0.4 and 4.1.3 are much faster. Also no test was conducted against tomcat 3.3.1. In fine we'd like to have more details on benchmarks used (JSP/Servlet/Static pages) to be able to replay them -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
FW: apt-get rpms ?
Hum, it seems apt has been discussed (planned/installed ?) BTW, should we package a commons-logging-1.0.1cvs or stay with commons-logging-1.0 ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 6:55 PM To: Tomcat Developers List Subject: apt-get rpms ? Henri, Any chance you will apt-enable the jpackage.org repository ? I love apt-get ( the RPM version ), it saves you a lot of time ( unfortunately not too many sources ). Costin On Tue, 11 Jun 2002, GOMEZ Henri wrote: BTW, all required OSS rpms needed to build tc 4.1.3 are available at jpackage.org : TC 4.1.3 rpm should be out really soon ... - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: GOMEZ Henri Sent: Tuesday, June 11, 2002 6:10 PM To: Tomcat Developers List Subject: RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample http://jakarta.apache.org/builds/jakarta-commons/release/common s-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? Do you speak about releasing commons-logging 1.0.1 ? -- 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] -- 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/jk/native2/common jk_signal.c jk_user.c
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 12. lipanj 2002 0:09 To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_signal.c jk_user.c costin 2002/06/11 15:09:11 Added: jk/native2/common jk_signal.c jk_user.c Log: Moved the signal and user handling to 'normal' jk components. ( to keep the jni simple ) Revision ChangesPath 1.1 jakarta-tomcat-connectors/jk/native2/common/jk_signal.c Can you tell me what is the final goal of implementing the signals? I ask you that because I'm working on a something simillar I hope, and more powerfull then standard signals offer. Basically it's a concept of apache server module hooks implemented on a module level, with the abillity to add the custom callback functions on the C and on the Java side. On the other hand it would be platform independent. The only drawback is that the APR has to be enabled. MT. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_endpoint.c
jfclere 2002/06/12 02:56:57
Modified:jk/native2/common jk_endpoint.c
Log:
Prevent core when createSlot fails.
Revision ChangesPath
1.19 +7 -1 jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c
Index: jk_endpoint.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- jk_endpoint.c 10 Jun 2002 21:55:06 - 1.18
+++ jk_endpoint.c 12 Jun 2002 09:56:57 - 1.19
@@ -86,8 +86,14 @@
snprintf( shmName, 128, epStat.%d, wEnv-childId );
wEnv-epStat=wEnv-shm-createSlot( env, wEnv-shm, shmName, 8096 );
+if (wEnv-epStat==NULL) {
+env-l-jkLog(env, env-l, JK_LOG_ERROR,
+ workerEnv.init() create slot %s failed\n, shmName
);
+return JK_ERR;
+}
wEnv-epStat-structCnt=0;
-env-l-jkLog(env, env-l, JK_LOG_ERROR, workerEnv.init() create slot
%s\n, shmName );
+env-l-jkLog(env, env-l, JK_LOG_ERROR,
+ workerEnv.init() create slot %s\n, shmName );
}
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_endpoint.c
The core was the following:
+++
(gdb) where
#0 jk2_endpoint_init (env=0x8108b40, bean=0x8157de0)
at ../../common/jk_endpoint.c:89
#1 0x403b13ab in jk2_workerEnv_addEndpoint (env=0x8108b40, wEnv=0x80f2668,
ep=0x8157e58) at ../../common/jk_workerEnv.c:583
#2 0x403b26de in jk2_worker_ajp13_getEndpoint (env=0x8108b40,
ajp13=0x810f428, eP=0xb518) at ../../common/jk_worker_ajp13.c:599
#3 0x403b276c in jk2_worker_ajp13_service (env=0x8108b40, w=0x810f428,
s=0x8155db8) at ../../common/jk_worker_ajp13.c:623
#4 0x403b73b6 in jk2_handler (r=0x814fda0)
at ../../server/apache2/mod_jk2.c:600
+++
The patch did not help because the return codes are not tested... (It cores
somewhere else :-((.
The real problem is why the createSlot fails!
[EMAIL PROTECTED] wrote:
jfclere 2002/06/12 02:56:57
Modified:jk/native2/common jk_endpoint.c
Log:
Prevent core when createSlot fails.
Revision ChangesPath
1.19 +7 -1 jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c
Index: jk_endpoint.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_endpoint.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- jk_endpoint.c 10 Jun 2002 21:55:06 - 1.18
+++ jk_endpoint.c 12 Jun 2002 09:56:57 - 1.19
@@ -86,8 +86,14 @@
snprintf( shmName, 128, epStat.%d, wEnv-childId );
wEnv-epStat=wEnv-shm-createSlot( env, wEnv-shm, shmName, 8096 );
+if (wEnv-epStat==NULL) {
+env-l-jkLog(env, env-l, JK_LOG_ERROR,
+ workerEnv.init() create slot %s failed\n,
shmName );
+return JK_ERR;
+}
wEnv-epStat-structCnt=0;
-env-l-jkLog(env, env-l, JK_LOG_ERROR, workerEnv.init() create
slot %s\n, shmName );
+env-l-jkLog(env, env-l, JK_LOG_ERROR,
+ workerEnv.init() create slot %s\n, shmName );
}
}
--
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 9772] - RequestDispatcher.forward(resource) does not perform necessary checks
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=9772. 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=9772 RequestDispatcher.forward(resource) does not perform necessary checks [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE | --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 11:30 --- Not checking security constraints on forwarded requests is part of the servlet spec. Where? Checked Servlet 2.2 and 2.3 spec and could not find such a documentation. Anyway: there is also NO spec which tells that a check must be performed, but security-constraints without checking do not make real sense. Also all other servlet-containers to perform a checking within their forward() method. If forward() does not need to perform security checks: how can I redirect the configured (form-based) login-page to the browser? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JNDI with a custom factory not working
Hi, I am having a problem trying to use a custom factory with JNDI. I get an exception froom org.apache.naming.factory.ResourceFactory. I have added debug and it appears that my factory parameter is not being picked up from the server.xml. Can somebody familiar with the naming code point me to the classes I need to look at to trace this problem. Alternatively, if somebody can confirm that the JNDI-Howto example for a custom beanFactory works correctly in 4.1 (I have tried it and it doesn't) then I will look at my configuration again. Regards, Arshad -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Small help
Hi all, I have a small problem. I am trying out Session Replication in Tomcat 4.0.3. But it does not work. In the site theserver.com there was a detailed step by step installation procedure. I tried out that but it still does not work. They had mentioned 2 test programs to try out if it did not work java org.javagroups.tests.McastReceiverTest -mcast_addr 224.10.10.10 -port . Then start McastSenderTest: java org.javagroups.tests.McastSenderTest -mcast_addr 224.10.10.10 -port . But these 2 are not present in the jar files. Anybody has a clue With Best Regards Jagan K Samuel With Best Regards Jagan K Samuel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
ClassLoader Bug?
I was trying to get Axis running on Tomcat 4.0.3,
4.0.4b3 and 4.1.3b and had the same problem with all
of them. I finally got it to run but, had to spread
the Jars and class files around to do it.(Note, I was
able to get 4.0.4 beta3 Windows install to work but,
as I deploy on Linux, this isn't an option)
Details I used to get it to work.
1) Move the jaxrpc.jar to a higher level in the
classloaders such as common/lib or shared/lib. This
is to get around the ClassNotFoundException on class
javax.xml.soap.SoapBody
2) Extract all the files from tt-bytecode.jar and
rebuild the jar. This is to get around a
SecurityException package com.techtrader (Funny, Im
not even running a SecurityManager)
3) Extract the classes from jaxrpc.jar and put the
classes under WEB-INF/classes. This is to get around
the NoSuchMethodError (Yes, Error not Exception) on
the call in
org.apache.axis.deployment.wsdd.WSDDDeployment to
tm.setSupportedEncodings(new String[]
{encodingStyle}); tm is of type interface
org.apache.axis.encoding.TypeMapping which extends
javax.xml.rpc.encoding.TypeMapping. The requirement
for the method setSupportedEncodings is in javax
version and Tomcat doesnt see it for some reason.
Note, extracting these still requires the jaxrpc.jar
to be in a higher classloader, if you remove it the
Exception described in 1 reoccurs.
After I did this, it successfully ran on Tomcat 4.0.3
on Linux, 4.0.3 on Win2K, 4.0.4b3 on Win2k and 4.1.3b
on Win2k
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Do scripts kill the HTTPsession object?
When I push down scripts to a client by putting something like Script LANGUAGE = 'JavaScript' SRC ='wwwroot/intranet/includes/menuBar.js'/Script in the document - all of a sudden I can no longer store or retrieve values from the HTTPsession object. I have to restart the server to get it back. Does anyone know why? My background is with IIS and I know this works fine in that environment [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_shm.c jk_workerEnv.c jk_worker_ajp13.c
jfclere 2002/06/12 05:40:17
Modified:jk/native2/common jk_shm.c jk_workerEnv.c jk_worker_ajp13.c
Log:
Prevent the core when getSlot() failed.
Revision ChangesPath
1.27 +10 -8 jakarta-tomcat-connectors/jk/native2/common/jk_shm.c
Index: jk_shm.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_shm.c,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- jk_shm.c 10 Jun 2002 21:55:06 - 1.26
+++ jk_shm.c 12 Jun 2002 12:40:17 - 1.27
@@ -447,16 +447,18 @@
int slotId;
int i;
jk_shm_slot_t *slot;
-
-for( i=1; ishm-head-lastSlot; i++ ) {
-slot= shm-getSlot( env, shm, i );
-if( strncmp( slot-name, name, strlen(name) ) == 0 ) {
-return slot;
+
+if (shm-head!=NULL) {
+for( i=1; ishm-head-lastSlot; i++ ) {
+slot= shm-getSlot( env, shm, i );
+if( strncmp( slot-name, name, strlen(name) ) == 0 ) {
+return slot;
+}
}
+/* New slot */
+/* XXX interprocess sync */
+slotId=shm-head-lastSlot++;
}
-/* New slot */
-/* XXX interprocess sync */
-slotId=shm-head-lastSlot++;
slot=shm-getSlot( env, shm, slotId );
if( slot==NULL ) return NULL;
1.54 +3 -2 jakarta-tomcat-connectors/jk/native2/common/jk_workerEnv.c
Index: jk_workerEnv.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_workerEnv.c,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- jk_workerEnv.c10 Jun 2002 21:55:06 - 1.53
+++ jk_workerEnv.c12 Jun 2002 12:40:17 - 1.54
@@ -580,7 +580,8 @@
wEnv-endpointMap-add( env, wEnv-endpointMap, ep-mbean-localName, ep );
ep-mbean-id=pos;
-ep-mbean-init( env, ep-mbean );
+if (ep-mbean-init( env, ep-mbean )==JK_ERR)
+return JK_ERR;
return JK_OK;
}
1.32 +14 -5 jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c
Index: jk_worker_ajp13.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worker_ajp13.c,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- jk_worker_ajp13.c 10 Jun 2002 21:55:06 - 1.31
+++ jk_worker_ajp13.c 12 Jun 2002 12:40:17 - 1.32
@@ -561,6 +561,7 @@
{
jk_endpoint_t *e = NULL;
jk_bean_t *jkb;
+int ret;
if( ajp13-secret ==NULL ) {
}
@@ -596,17 +597,23 @@
*eP = e;
-ajp13-workerEnv-addEndpoint( env, ajp13-workerEnv, e );
+ret = ajp13-workerEnv-addEndpoint( env, ajp13-workerEnv, e );
}
if( ajp13-cs != NULL )
ajp13-cs-unLock( env, ajp13-cs );
-if( ajp13-mbean-debug 0 )
-env-l-jkLog(env, env-l, JK_LOG_INFO,
+if( ajp13-mbean-debug 0 ) {
+if (ret==JK_OK)
+env-l-jkLog(env, env-l, JK_LOG_INFO,
ajp13.getEndpoint(): Created endpoint %s %s \n,
ajp13-mbean-name, jkb-name);
+else
+env-l-jkLog(env, env-l, JK_LOG_INFO,
+ ajp13.getEndpoint(): endpoint creation %s %s failed\n,
+ ajp13-mbean-name, jkb-name);
+}
-return JK_OK;
+return ret;
}
/*
@@ -620,7 +627,9 @@
jk_endpoint_t *e;
/* Get endpoint from the pool */
-jk2_worker_ajp13_getEndpoint( env, w, e );
+err=jk2_worker_ajp13_getEndpoint( env, w, e );
+if (err!=JK_OK)
+ return err;
#ifdef HAS_APR
if( s-uriEnv!=NULL s-uriEnv-timing == JK_TRUE ) {
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/server/apache2 jk_logger_apache2.c
jfclere 2002/06/12 05:42:25
Modified:jk/native2/server/apache2 jk_logger_apache2.c
Log:
Allow to switch on the trace of env.
Revision ChangesPath
1.26 +2 -1
jakarta-tomcat-connectors/jk/native2/server/apache2/jk_logger_apache2.c
Index: jk_logger_apache2.c
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache2/jk_logger_apache2.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- jk_logger_apache2.c 7 Jun 2002 23:45:30 - 1.25
+++ jk_logger_apache2.c 12 Jun 2002 12:42:25 - 1.26
@@ -170,7 +170,8 @@
if( strcmp( name, level )==0 ) {
_this-level = jk2_logger_file_parseLogLevel(env, value);
-if( _this-level == 0 ) {
+if( _this-level == JK_LOG_DEBUG_LEVEL ) {
+env-debug = 1;
/* _this-jkLog( env, _this, JK_LOG_ERROR, */
/* Level %s %d \n, value, _this-level ); */
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jasper2: @page buffer syntax
On June 11, 2002 10:19 pm, you wrote: There are plenty of JSP1.1 pages out there, this will require people to rewrite the pages just to add a 'kb' suffix ( which is pretty weird by itself, almost everything else uses k, and is redundant - if the size can only be specified in kb, there is no reason to require the suffix ). For one thing I don't think a LOT of people actually specify the buffer size (of course those who DO will jump in to prove me wrong, and those who don't will remain silent :-)). For another, memory is getting bigger quickly, and having sizes of things specified unambiguously - in such a way that it can be understood by someone who can't quote the spec from memory - is a Good Thing. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
Did there is still opened bugs in mod_jk 1.2.0 (jtc/native) which could prevent us to make a release ? Appart the AP 2.0 error when worker didn't exist. = Server error! Error message: handler jakarta-servlet not found for: If you think this is a server error, please contact the webmaster Error 500 hgo1.slib.com Wed Jun 12 16:04:27 2002 Apache/2.0.36 (Unix) mod_ssl/2.0.36 OpenSSL/0.9.6 DAV/2 mod_jk/1.2.0 - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: GOMEZ Henri Sent: Tuesday, June 11, 2002 10:20 AM To: Tomcat Developers List Subject: RE: jk 1.2 freese/snap time in JTC ? +1 for mod_jk 1.2.0 for Apache 1.3.24. It's been running stable on my systems for a really long time now. Not sure if the bug related to not picking up the index pages when used with Apache 2.0.35 still exists... Anyone knows? To find the thread, search this list for this: 'Apache 2.0.35 and mod_jk 1.2.0'. I've posted the question on 2002-04-07. Hum, It's the bad error report when you specify a worker which didn't exist. I'm not sure if Costin fixed it... Bojan On Mon, 2002-06-10 at 23:26, GOMEZ Henri wrote: Did there is still work on progress in JK (native) in JTC ? If not, it could be the good moment to make a 1.2.0 snapshot, and ask contributers/friends to generate binaries on there platforms. Regards - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -- 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] -- 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 3839] - Problem bookmarking login page
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=3839. 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=3839 Problem bookmarking login page --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 14:13 --- That looks like a valid WORKAROUND but I believe this is something that I as a developer shouldn't have to handle. This should all be handled seemlessly by the container. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c
hgomez 2002/06/12 07:31:09 Modified:jk/native/apache-2.0 mod_jk.c Log: Fix the incorrect error reported when a worker is defined but didn't exist (reported by Bojan) Revision ChangesPath 1.45 +4 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c Index: mod_jk.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- mod_jk.c 8 May 2002 00:45:33 - 1.44 +++ mod_jk.c 12 Jun 2002 14:31:09 - 1.45 @@ -1324,6 +1324,9 @@ return OK;/* NOT r-status, even if it has changed. */ } } + else + return HTTP_INTERNAL_SERVER_ERROR; + } return DECLINED; -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c
This should fix the problem reported by Bojan. What about tagging jtc for jk_1_2_0 release ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 4:31 PM To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c hgomez 2002/06/12 07:31:09 Modified:jk/native/apache-2.0 mod_jk.c Log: Fix the incorrect error reported when a worker is defined but didn't exist (reported by Bojan) Revision ChangesPath 1.45 +4 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c Index: mod_jk.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- mod_jk.c 8 May 2002 00:45:33 - 1.44 +++ mod_jk.c 12 Jun 2002 14:31:09 - 1.45 @@ -1324,6 +1324,9 @@ return OK;/* NOT r-status, even if it has changed. */ } } +else +return HTTP_INTERNAL_SERVER_ERROR; + } return DECLINED; -- 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/jk/native2/common jk_signal.cjk_user.c
On Wed, 12 Jun 2002, Mladen Turk wrote: Can you tell me what is the final goal of implementing the signals? Well, my first 'itch' was the ability for a java program to send a SIGHUP to apache. Beeing able to receive a SIGHUP seemed interesting too :-) I ask you that because I'm working on a something simillar I hope, and more powerfull then standard signals offer. Basically it's a concept of apache server module hooks implemented on a module level, with the abillity to add the custom callback functions on the C and on the Java side. The signals in jk are only for use by Java, and mostly for experimental or specialized use. One of my goals is to explore using OS-specific features, which are not typically available to java programs ( because not portable ). I believe this will allow better integration between java and the rest of the world. Some may think that eventually all software in the world will be written in java, and all OS-es will have exactly the same features since nobody will be able to use specific features. Until this happens, I think it would be nice to use the full power of the OS and integrate with the 'legacy' languages ( or C# will do it ) :-) On the other hand it would be platform independent. The only drawback is that the APR has to be enabled. That would be great - and jkjni requires APR anyway. You may notice the java class is called AprImpl, one of the goals is to expose all APR features that are not available in java. Initially the class was just a jni wrapper to APR functions. Unfortunately the JNI performance characteristics made this a bad solution, so now we use all the tricks with buffer pinning to get around this. If your abstraction in APR will support signals ( as a particular case ), then jk_signal will just go away. If not, I think it is valuable to provide both - unix signals are one of the things that java lacks and are usefull for integrating java with other applications. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9650] - mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location
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=9650. 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=9650 mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:04 --- Created an attachment (id=2067) Tina's httpd.conf configuration file -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9650] - mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location
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=9650. 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=9650 mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:05 --- Created an attachment (id=2068) Tina's server.xml for Tomcat. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
De: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Enviado el: 12 de junio de 2002 16:11 Did there is still opened bugs in mod_jk 1.2.0 (jtc/native) which could prevent us to make a release ? I was having problems with JNI worker, internal tomcat 3.3 test hang tomcat AFAIK. we need some time to test jk 1.2 under IIS.. AFAIK there is some problems with file names, the given reg file, docs and binaries has different names for the dll, and they do not match, this problem it's the most reported one in tomcat-user against 4.0+jk1.2+IIS, the people do not realize that they need to change things to match the real names.. i dont know where is exactly the problem.. if anyone remember I'll try to solve it next days.. Saludos , Ignacio J. Ortega msg28835/bin0.bin Description: application/ms-tnef -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9650] - mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location
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=9650. 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=9650 mod_webapp causes Apache to go into infinite loop if application is deployed outside of tomcat default webapp location --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:10 --- Tina, from what I can see, you should try to change this line WebAppDeploy c:/sof...se/webapps warpConnection /softwarehouse into WebAppDeploy /sof...se/webapps warpConnection /softwarehouse or by fully specifying the url as WebAppDeploy file:///sof...se/webapps warpConnection /softwarehouse Then make sure you have the WEB_INF directory in c:\softwarehouse\ webapps (so your web.xml must be in c:\softwarehouse\webapps\WEB- INF\web.xml... Can you please check this and report back? Thank you... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
I was having problems with JNI worker, internal tomcat 3.3 test hang tomcat AFAIK. Urg, who could help in JNI/TC3.3 ? we need some time to test jk 1.2 under IIS.. You're the boss here ;) AFAIK there is some problems with file names, the given reg file, docs and binaries has different names for the dll, and they do not match, this problem it's the most reported one in tomcat-user against 4.0+jk1.2+IIS, the people do not realize that they need to change things to match the real names.. i dont know where is exactly the problem.. if anyone remember I'll try to solve it next days.. Ok -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native build.xml
mmanders2002/06/12 08:30:01
Modified:jk/native build.xml
Log:
Updated to match new libc directory structure for NetWare builds.
Revision ChangesPath
1.35 +1 -0 jakarta-tomcat-connectors/jk/native/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/build.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- build.xml 30 May 2002 07:12:28 - 1.34
+++ build.xml 12 Jun 2002 15:30:01 - 1.35
@@ -164,6 +164,7 @@
include name=${java.home}/../include/netware if=netware /
include name=${java.home}/../include/linux if=linux/
include name=${novelllibc.dir}/include if=netware /
+ include name=${novelllibc.dir}/include/winsock if=netware /
/includes
depends
fileset dir=${native.dir}/common includes=*.h /
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7656] - Webapplications deployed using PUT don't survive a tomcat restart
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=7656. 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=7656 Webapplications deployed using PUT don't survive a tomcat restart [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:30 --- This doesn't seem to be working in 4.1.4. The extracted/compiled webapp files remain in work, but the app itself isn't available; it's necessary to deploy the app again. I'm using the catalina-ant tasks to install/uninstall the app, if it makes a difference. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native/apache-1.3 mod_jk.c
mmanders2002/06/12 08:51:48
Modified:jk/native/apache-1.3 mod_jk.c
Log:
Added check for NO_GETTIMEOFDAY since gettimeofday isn't supported on all platforms.
Revision ChangesPath
1.27 +5 -1 jakarta-tomcat-connectors/jk/native/apache-1.3/mod_jk.c
Index: mod_jk.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-1.3/mod_jk.c,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- mod_jk.c 21 Apr 2002 22:57:11 - 1.26
+++ mod_jk.c 12 Jun 2002 15:51:48 - 1.27
@@ -1526,9 +1526,11 @@
s.ws_private = private_data;
s.pool = private_data.p;
+#ifndef NO_GETTIMEOFDAY
if(conf-format != NULL) {
gettimeofday(tv_begin, NULL);
}
+#endif
if(init_ws_service(private_data, s, conf)) {
jk_endpoint_t *end = NULL;
@@ -1553,6 +1555,7 @@
}
end-done(end, l);
}
+#ifndef NO_GETTIMEOFDAY
if(conf-format != NULL) {
char *duration = NULL;
char *status = NULL;
@@ -1568,6 +1571,7 @@
ap_table_setn(r-notes, JK_DURATION, duration);
request_log_transaction(r,conf);
}
+#endif
}
jk_close_pool(private_data.p);
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9772] - RequestDispatcher.forward(resource) does not perform necessary checks
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=9772. 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=9772 RequestDispatcher.forward(resource) does not perform necessary checks --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:57 --- Java Servlet Specification Version 2.3 SRV.12.2 Declarative Security The security model does not apply when a servlet uses the RequestDispatcher to invoke a static resource or servlet using a forward or an include. The theory is that 2.3 is a clarification of 2.2 when they address the same issues. You can do an HTTP redirect over to the security page instead of using an internal forward. (Is this really a duplicate of 5722 Forward to a page that have no extension displays a blank page?) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9715] - Context ... cached=false/ appears to still cache
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=9715. 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=9715 Context ... cached=false/ appears to still cache [EMAIL PROTECTED] changed: What|Removed |Added Summary|'Out of Memory' error with |Context ... |static html pages |cached=false/ appears to ||still cache --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 15:59 --- Updated/Changed the summary -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat/IIS Integration url request.getParameter()
Hi!
I've tried to search FAQ's and newgroups and haven't
been able to find anything. Please forgive me if its
been answered.
With the Tomcat 3.3/IIS forwarding jsp responses, it
seems as though any url parameters are not being
forwarded and are returning NULL. ie.
http://localhost/index.jsp?username=blahpassword=yadayadayda
The username/password requests are not returning
anything. I can confirm this when I go to the port
tomcat is running on behind the scenes, these
paramters are coming through.
Is there a class or something I need to do in order to
get these forwarded?
Thanks
-Matt
=
int myName() {
cout -Matt Fury \n;
return 0;
}
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 5829] - StandardManager needs to cope with sessions throwing exception in read/write
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=5829. 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=5829 StandardManager needs to cope with sessions throwing exception in read/write --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 16:11 --- I was wondering, why are things being placed into the session that are not serializable. Doesnt it seem like that is a bad idea? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7656] - Webapplications deployed using PUT don't survive a tomcat restart
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=7656. 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=7656 Webapplications deployed using PUT don't survive a tomcat restart [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 16:33 --- You have to use deploy/undeploy, and this now works. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
watchdog, servletapi, karma
I'd like to check in some (fairly minor) fixes to jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have the karma. Is it a big deal to get added? I wasn't sure if servletapi and watchdog were closely tied to tomcat or their own whole thing with separate administration. It looks like there's been no recent traffic to servletapi-dev, and minimal traffic to watchdog-dev, instead everybody just posts to tomcat-dev, so... -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
On Wed, 12 Jun 2002, GOMEZ Henri wrote: I was having problems with JNI worker, internal tomcat 3.3 test hang tomcat AFAIK. Urg, who could help in JNI/TC3.3 ? Can we just put it in the release notes, and focus on the jni worker in jk2 ? ( i.e. people who use the JNI worker with modjk1.1 should not upgrade ). This affects only iPlanet and IIS with tomcat3.3. Has anyone 'volunteered' as release manager for jk1.2 ? If someone does, he can decide on the 'mustfix' bugs for the release, and if this is listed I'll fix it. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: watchdog, servletapi, karma
I'd like to check in some (fairly minor) fixes to jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have the karma. Is it a big deal to get added? Will you apply some patches to jakarta-servletapi-4 code ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 build.properties.sample build.xml
jfclere 2002/06/12 09:47:05
Modified:.build.properties.sample build.xml
Log:
Arrange commons-logging... We have to use cvs until it gets released.
Revision ChangesPath
1.43 +3 -2 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- build.properties.sample 10 Jun 2002 05:27:18 - 1.42
+++ build.properties.sample 12 Jun 2002 16:47:05 - 1.43
@@ -82,7 +82,8 @@
commons-logging.lib=${commons-logging.home}
commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
commons-logging.jar=${commons-logging.lib}/commons-logging.jar
-commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
+commons-logging.loc=jakarta-commons/logging
+#commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
# - Java Naming and Directory Interface (JNDI), version 1.2 or later -
1.72 +17 -0 jakarta-tomcat-4.0/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- build.xml 6 Jun 2002 04:23:27 - 1.71
+++ build.xml 12 Jun 2002 16:47:05 - 1.72
@@ -457,10 +457,27 @@
param name=sourcefile value=${commons-digester.loc}/
param name=destfile value=${commons-digester.jar}/
/antcall
+
+!-- we need the release to happend, in the meantime use cvs...
antcall target=downloadgz
param name=sourcefile value=${commons-logging.loc}/
param name=destfile value=${commons-logging.jar}/
/antcall
+--
+antcall target=cvsbuild
+ param name=location value=${commons-logging.loc}/
+ param name=subdir value=${commons-logging.home}/
+ param name=destfile value=${commons-logging.jar}/
+/antcall
+copy
+ file=${commons-logging.home}/dist/commons-logging.jar
+ tofile=${commons-logging.jar}
+/
+copy
+ file=${commons-logging.home}/dist/commons-logging-api.jar
+ tofile=${commons-logging-api.jar}
+/
+
antcall target=downloadgz
param name=sourcefile value=${regexp.loc}/
param name=destfile value=${regexp.jar}/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
I was having problems with JNI worker, internal tomcat 3.3 test hang tomcat AFAIK. Urg, who could help in JNI/TC3.3 ? Can we just put it in the release notes, and focus on the jni worker in jk2 ? ( i.e. people who use the JNI worker with modjk1.1 should not upgrade ). This affects only iPlanet and IIS with tomcat3.3. Has anyone 'volunteered' as release manager for jk1.2 ? If someone does, he can decide on the 'mustfix' bugs for the release, and if this is listed I'll fix it. Hum, what's should do the release manager ? Also could we tag jtc to jk_1_2_0_release but do tarball containing only jk/native ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: watchdog, servletapi, karma
GOMEZ Henri wrote: I'd like to check in some (fairly minor) fixes to jakarta-servletapi-4 and jakarta-watchdog-4.0, but I don't have the karma. Is it a big deal to get added? Will you apply some patches to jakarta-servletapi-4 code ? Well, I wanted to apply a patch for a bug I reported a while back where GenericServlet.init() and destroy() send messages (saying init and destroy) to log(). It's not a showstopper, but it's very annoying. If someone else wants to remove the two log() statments, that would be great. Or do you mean you (Henri Gomez) have some patches and want somebody to apply them? If I had the karma, and the patches were righteous (and I suspect they would be), then sure. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: watchdog, servletapi, karma
Well, I wanted to apply a patch for a bug I reported a while back where GenericServlet.init() and destroy() send messages (saying init and destroy) to log(). It's not a showstopper, but it's very annoying. If someone else wants to remove the two log() statments, that would be great. Or do you mean you (Henri Gomez) have some patches and want somebody to apply them? If I had the karma, and the patches were righteous (and I suspect they would be), then sure. No, I saw a problem here since servlet-api-4.0 is the OFFICIAL servlet 2.3/jsp1.2 API and may not change without (wide) notice. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jasper2: @page buffer syntax
On Wed, 12 Jun 2002, Ian Darwin wrote: For one thing I don't think a LOT of people actually specify the buffer size (of course those who DO will jump in to prove me wrong, and those who don't will remain silent :-)). For another, memory is getting bigger quickly, and having sizes of things specified unambiguously - in such a way that it can be understood by someone who can't quote the spec from memory - is a Good Thing. Well, having the 'kb' suffix will certainly avoid confusion for the metric-system people ( who may believe that's in kilograms or kilometers ). It is certainly confusing for programmers ( were most of the time the 'k' suffix is used, and the default suffix is optional ). I'm very sensitive to backward compatibility, and it drives me crazy when I see this kind of changes - I understand deprecating Thread.stop(), or things where any decent argument exists, but changing a syntax in an incompatible way for estetic reasons is unacceptable. As for the pages that'll brake - well, tomcat4.0 examples ( part of the JSP1.2 RI ! ) are one case ( see include.jsp ). Note that the size was already ( in jsp1.1 ) in kilobytes, the only change is in 1.2 is to make it mandatory to use a 'kb' suffix ( and thus ilegal to use the previously legal values, without kb ). I know strict compliance is important ( almost as important as backward compatibility on my scale ), and the bug is not in jasper but in the spec. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9164] - Incompatible type for method: handlePageException
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=9164.
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=9164
Incompatible type for method: handlePageException
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2002-06-12 17:00 ---
I downloaded and installed the Windows version of Tomcat (jakarta-tomcat-
4.0.3.exe) on 31 May 2002. I used 'jar' to extract
javax.servlet.jsp.PageContext from %TOMCAT_HOME%\common\lib\servlet.jar,
and 'javap -public' to examine its members. Here is the result:
Compiled from PageContext.java
public abstract class javax.servlet.jsp.PageContext extends java.lang.Object {
public static final int PAGE_SCOPE;
public static final int REQUEST_SCOPE;
public static final int SESSION_SCOPE;
public static final int APPLICATION_SCOPE;
public static final java.lang.String PAGE;
public static final java.lang.String PAGECONTEXT;
public static final java.lang.String REQUEST;
public static final java.lang.String RESPONSE;
public static final java.lang.String CONFIG;
public static final java.lang.String SESSION;
public static final java.lang.String OUT;
public static final java.lang.String APPLICATION;
public static final java.lang.String EXCEPTION;
public javax.servlet.jsp.PageContext();
public abstract java.lang.Object findAttribute(java.lang.String);
public abstract void forward(java.lang.String) throws
javax.servlet.ServletException, java.io.IOException;
public abstract java.lang.Object getAttribute(java.lang.String);
public abstract java.lang.Object getAttribute(java.lang.String, int);
public abstract java.util.Enumeration getAttributeNamesInScope(int);
public abstract int getAttributesScope(java.lang.String);
public abstract java.lang.Exception getException();
public abstract javax.servlet.jsp.JspWriter getOut();
public abstract java.lang.Object getPage();
public abstract javax.servlet.ServletRequest getRequest();
public abstract javax.servlet.ServletResponse getResponse();
public abstract javax.servlet.ServletConfig getServletConfig();
public abstract javax.servlet.ServletContext getServletContext();
public abstract javax.servlet.http.HttpSession getSession();
public abstract void handlePageException(java.lang.Exception) throws
javax.servlet.ServletException, java.io.IOException;
public abstract void include(java.lang.String) throws
javax.servlet.ServletException, java.io.IOException;
public abstract void initialize(javax.servlet.Servlet,
javax.servlet.ServletRequest, javax.servlet.ServletResponse, java.lang.String,
boolean, int, boolean) throws java.io.IOException,
java.lang.IllegalStateException, java.lang.IllegalArgumentException;
public javax.servlet.jsp.JspWriter popBody();
public javax.servlet.jsp.tagext.BodyContent pushBody();
public abstract void release();
public abstract void removeAttribute(java.lang.String);
public abstract void removeAttribute(java.lang.String, int);
public abstract void setAttribute(java.lang.String, java.lang.Object);
public abstract void setAttribute(java.lang.String, java.lang.Object, int);
}
Note that there is no
public abstract void handlePageException(java.lang.Throwable) throws
javax.servlet.ServletException, java.io.IOException;
Therefore, I suggest that the problem is with the distribution. Could you fix
this please?
Thanks,
Chris (mailto:[EMAIL PROTECTED]).
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample build.xml
[EMAIL PROTECTED] wrote: jfclere 2002/06/12 09:47:05 Modified:.build.properties.sample build.xml Log: Arrange commons-logging... We have to use cvs until it gets released. Thanks for fixing that :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
On Wed, 12 Jun 2002, GOMEZ Henri wrote: Has anyone 'volunteered' as release manager for jk1.2 ? If someone does, he can decide on the 'mustfix' bugs for the release, and if this is listed I'll fix it. Hum, what's should do the release manager ? Build the 'official' release, review the bugs and decide what bugs must be fixed, putting the release to a vote and making the announcements. And of course, make sure the stars are in the right position and all the software we depend on is released first and has all the fixes we need ( for jk that's not an issue yet ). Also could we tag jtc to jk_1_2_0_release but do tarball containing only jk/native ? When the official build is made, yes. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: watchdog, servletapi, karma
GOMEZ Henri wrote: No, I saw a problem here since servlet-api-4.0 is the OFFICIAL servlet 2.3/jsp1.2 API and may not change without (wide) notice. Yes, but there's a difference between changing the API (which is the job of the servlet spec jsr team) and fixing bugs in the implementation classes. I'd be perfectly happy if somebody else would just fix the bug, but nobody seems to be maintaining the code at the moment. I propose you to make a PROPOSAL for servletapi4 patch to tomcat-dev list. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: watchdog, servletapi, karma
Christopher, You can send me the Watchdog patches and I'll look them over. Thanks, -rl On Wed, 2002-06-12 at 12:01, Christopher K. St. John wrote: GOMEZ Henri wrote: No, I saw a problem here since servlet-api-4.0 is the OFFICIAL servlet 2.3/jsp1.2 API and may not change without (wide) notice. Yes, but there's a difference between changing the API (which is the job of the servlet spec jsr team) and fixing bugs in the implementation classes. I'd be perfectly happy if somebody else would just fix the bug, but nobody seems to be maintaining the code at the moment. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- 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 9164] - Incompatible type for method: handlePageException
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=9164. 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=9164 Incompatible type for method: handlePageException [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 17:18 --- I have no idea how it happened, but you have the old servlet API JAR there. The installable package does include the right version of the servlet API. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat/IIS Integration url request.getParameter()
Matt,
I recall there being a bug related to this in the
isapi_redirect.dll for Tomcat 3.3. For security, the dll
normalizes the URI before checking to see if it should be
forwarded to Tomcat. If the URI was shortened because
of this normalization, the query parameters would be lost.
This is fixed in the isapi_redirect.dll distributed with
Tomcat 3.3.1 and is fixed in the jakarta-tomcat-connectors'
isapi_redirector.dll (note the added or before .dll).
If you are using the isapi_redirect.dll from Tomcat 3.3,
try the one from Tomcat 3.3.1 and see if it fixes your
problem. You will find it here:
http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1/bin/win32/i386/
Cheers,
Larry
-Original Message-
From: Matt Fury [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 12:08 PM
To: [EMAIL PROTECTED]
Subject: Tomcat/IIS Integration url request.getParameter()
Hi!
I've tried to search FAQ's and newgroups and haven't
been able to find anything. Please forgive me if its
been answered.
With the Tomcat 3.3/IIS forwarding jsp responses, it
seems as though any url parameters are not being
forwarded and are returning NULL. ie.
http://localhost/index.jsp?username=blahpassword=yadayadayda
The username/password requests are not returning
anything. I can confirm this when I go to the port
tomcat is running on behind the scenes, these
paramters are coming through.
Is there a class or something I need to do in order to
get these forwarded?
Thanks
-Matt
=
int myName() {
cout -Matt Fury \n;
return 0;
}
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
mailto:tomcat-dev- [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: jk 1.2 freese/snap time in JTC ?
Hum, what's should do the release manager ? Build the 'official' release, review the bugs and decide what bugs must be fixed, putting the release to a vote and making the announcements. May be we could team-up with Larry ? And of course, make sure the stars are in the right position and all the software we depend on is released first and has all the fixes we need ( for jk that's not an issue yet ). Also could we tag jtc to jk_1_2_0_release but do tarball containing only jk/native ? When the official build is made, yes. Ok Larry what about being RM for JTC/JK1.2.0 ? I'll help you on build unix (Linux i386, AIX), review BUGS and announce... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Missing files in connector-source
hi, = configure / make / make install is not possible. i can't find any configure-script in the connector-source-file jakarta-tomcat-connectors-4.0.2-01-src.tar.gz and so it's not possible to compile and install any connectors from the source (without cvs) thx for help oliver scorp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PROPOSAL] Minor fix for servletapi-4 GenericServlet
GOMEZ Henri wrote: I propose you to make a PROPOSAL for servletapi4 patch to tomcat-dev list. In the jakarta-servletapi-4 repository, the class: javax.servlet.GenericServlet has init() and destory() methods that call log(). While not specifically prohibited in the 2.3 spec, it results in unncessary output into logs. Also, it's annoying. My proposal is to remove the two log() statements from GenericServet.init() and GenericServlet.destory(). If somebody needs them for debugging, they can add them back into their local copy. This was reported as bug #7190. I've included a patch as an attachment to this message (it just removes the two log messages and updates the copyright date) -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com jsa4-gensrv.patch Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
Hi Henri, I haven't been very active of late with Tomcat 3.3.x due to being too busy with other things right now. I'm not sure when I would find the time for JTC RM duties at this moment. Cheers, Larry -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 1:28 PM To: Tomcat Developers List Subject: RE: jk 1.2 freese/snap time in JTC ? Hum, what's should do the release manager ? Build the 'official' release, review the bugs and decide what bugs must be fixed, putting the release to a vote and making the announcements. May be we could team-up with Larry ? And of course, make sure the stars are in the right position and all the software we depend on is released first and has all the fixes we need ( for jk that's not an issue yet ). Also could we tag jtc to jk_1_2_0_release but do tarball containing only jk/native ? When the official build is made, yes. Ok Larry what about being RM for JTC/JK1.2.0 ? I'll help you on build unix (Linux i386, AIX), review BUGS and announce... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat/IIS Integration url request.getParameter()
Great, I'll try it! Thanks. I would really like to run
Tomcat 4.0.3 but i was having problems setting it up.
The console was reporting Java errors when I went to
hit the page. But this discussion is for the other
newsgroup ;-)
-Matt
--- Larry Isaacs [EMAIL PROTECTED] wrote:
Matt,
I recall there being a bug related to this in the
isapi_redirect.dll for Tomcat 3.3. For security,
the dll
normalizes the URI before checking to see if it
should be
forwarded to Tomcat. If the URI was shortened
because
of this normalization, the query parameters would be
lost.
This is fixed in the isapi_redirect.dll distributed
with
Tomcat 3.3.1 and is fixed in the
jakarta-tomcat-connectors'
isapi_redirector.dll (note the added or before
.dll).
If you are using the isapi_redirect.dll from Tomcat
3.3,
try the one from Tomcat 3.3.1 and see if it fixes
your
problem. You will find it here:
http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.3.1/bin/win32/i386/
Cheers,
Larry
-Original Message-
From: Matt Fury [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 12:08 PM
To: [EMAIL PROTECTED]
Subject: Tomcat/IIS Integration url
request.getParameter()
Hi!
I've tried to search FAQ's and newgroups and
haven't
been able to find anything. Please forgive me if
its
been answered.
With the Tomcat 3.3/IIS forwarding jsp responses,
it
seems as though any url parameters are not being
forwarded and are returning NULL. ie.
http://localhost/index.jsp?username=blahpassword=yadayadayda
The username/password requests are not returning
anything. I can confirm this when I go to the port
tomcat is running on behind the scenes, these
paramters are coming through.
Is there a class or something I need to do in
order to
get these forwarded?
Thanks
-Matt
=
int myName() {
cout -Matt Fury \n;
return 0;
}
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
mailto:tomcat-dev-
[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]
=
int myName() {
cout -Matt Fury \n;
return 0;
}
__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 7827] - catalina.sh can't work in Cygwin environment
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=7827. 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=7827 catalina.sh can't work in Cygwin environment [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX | --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 18:40 --- I understand the above tons of hacks argument, however, if that is the case then everything in the scripts referencing cygwin should be removed so it does not appear to support cygwin. I just spent an hour searching the web because I thought There must be something wrong with my environment because catalina.sh obviously should work under cygwin because it does cygwin checks in several places. It makes no sense to have cygwin checks in this script if it's broken in cygwin. It would actually be easier to just apply the two line change noted in the original entry of this bug report than to remove all cygwin references. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Two TCs???
Do we have two seperate TCs in the development process? I see the v4.0.4-b3 release arouind 10th and 11th of May as well as v4.1.3-b release around 28th and 29th of May. What's going on? Pae [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/ [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Two TCs???
On Wed, 12 Jun 2002, Pae Choi wrote: Date: Wed, 12 Jun 2002 12:56:20 -0700 From: Pae Choi [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Cc: Tomcat Developers List [EMAIL PROTECTED] Subject: Two TCs??? Do we have two seperate TCs in the development process? I see the v4.0.4-b3 release arouind 10th and 11th of May as well as v4.1.3-b release around 28th and 29th of May. Active development of new features (such as substantially improved performance on JSP pages, and the new admin webapp) are taking place in the 4.1.x development tree. Because there is lots of new code here, the risk of new bugs is somewhat higher than on a stable release. Bugfix maintenance releases continue in the 4.0.x development tree so that people running production apps have a lower risk way to incorporate fixes for existing bugs -- but new features only go into the new version. What's going on? Same thing that happens in most major software development projects -- overlapping development cycles. Consider Apache (1.3.x versus 2.0.x), Linux (2.4 versus 2.5), and pretty much any other large scale product, and you'll see the same thing. Pae Craig [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/ [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/ -- 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: Two TCs???
Craig, Thank you for your reply as well as clarifying my previous inquiry. Best, Pae - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Cc: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, June 12, 2002 10:33 AM Subject: Re: Two TCs??? On Wed, 12 Jun 2002, Pae Choi wrote: Date: Wed, 12 Jun 2002 12:56:20 -0700 From: Pae Choi [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Cc: Tomcat Developers List [EMAIL PROTECTED] Subject: Two TCs??? Do we have two seperate TCs in the development process? I see the v4.0.4-b3 release arouind 10th and 11th of May as well as v4.1.3-b release around 28th and 29th of May. Active development of new features (such as substantially improved performance on JSP pages, and the new admin webapp) are taking place in the 4.1.x development tree. Because there is lots of new code here, the risk of new bugs is somewhat higher than on a stable release. Bugfix maintenance releases continue in the 4.0.x development tree so that people running production apps have a lower risk way to incorporate fixes for existing bugs -- but new features only go into the new version. What's going on? Same thing that happens in most major software development projects -- overlapping development cycles. Consider Apache (1.3.x versus 2.0.x), Linux (2.4 versus 2.5), and pretty much any other large scale product, and you'll see the same thing. Pae Craig [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/ [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/ -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9813] New: - typo in build.xml for sample servlet
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=9813.
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=9813
typo in build.xml for sample servlet
Summary: typo in build.xml for sample servlet
Product: Tomcat 4
Version: 4.0.3 Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Webapps:Examples
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
In this excerpt from build.xml, notice that the javadoc element is closed twice.
target name=javadoc depends=compile
description=Create Javadoc API documentation
mkdir dir=${dist.home}/docs/api/
javadoc sourcepath=src
destdir=${dist.home}/docs/api
packagenames=*/
classpath refid=compile.classpath/
/javadoc
/target
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] Minor fix for servletapi-4 GenericServlet
Christopher K. St. John wrote: In the jakarta-servletapi-4 repository, the class: javax.servlet.GenericServlet has init() and destory() methods that call log(). While not specifically prohibited in the 2.3 spec, it results in unncessary output into logs. Also, it's annoying. My proposal is to remove the two log() statements from GenericServet.init() and GenericServlet.destory(). If somebody needs them for debugging, they can add them back into their local copy. This was reported as bug #7190. I've included a patch as an attachment to this message (it just removes the two log messages and updates the copyright date) +1. This sounds reasonable to me. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: 12 de junio de 2002 18:46 Can we just put it in the release notes, and focus on the jni worker in jk2 ? ( i.e. people who use the JNI worker with modjk1.1 should not upgrade ). OK, i was only pointing to some problem i know of.., something to be at least documented.. i would not oppose, and if i would, i could try to fix it myself, no problem.. :) Has anyone 'volunteered' as release manager for jk1.2 ? If someone does, he can decide on the 'mustfix' bugs for the release, and if this is listed I'll fix it. The silence can be masked :) Could we do some kind of collective RM for that relase? it's at least possible to do a release this way? Put up a list of tasks, another of bugs, vote and comment in what to do.. and simply do it.. Do we need a (benevolent) dictator for this? ( please take it as a comment, no negative feelings, but it seems to me , that to find a RM for that release could be hard, and seems it's an important release to someone, not me, i could help, but not take the role myself ) Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [PROPOSAL] Minor fix for servletapi-4 GenericServlet
There is another question here. When log() is called no default log level is assigned to it so there is no way to prevent log() messages from cluttering the log files. What about a change to allow the setting of the log level for the log() method in server.xml or web.xml (or even giving it a its own log level) so then all the log() messages can be turned on and off.. -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 3:36 PM To: Tomcat Developers List Subject: Re: [PROPOSAL] Minor fix for servletapi-4 GenericServlet Christopher K. St. John wrote: In the jakarta-servletapi-4 repository, the class: javax.servlet.GenericServlet has init() and destory() methods that call log(). While not specifically prohibited in the 2.3 spec, it results in unncessary output into logs. Also, it's annoying. My proposal is to remove the two log() statements from GenericServet.init() and GenericServlet.destory(). If somebody needs them for debugging, they can add them back into their local copy. This was reported as bug #7190. I've included a patch as an attachment to this message (it just removes the two log messages and updates the copyright date) +1. This sounds reasonable to me. 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]
RE: jk 1.2 freese/snap time in JTC ?
On Wed, 12 Jun 2002, Ignacio J. Ortega wrote: Has anyone 'volunteered' as release manager for jk1.2 ? If someone does, he can decide on the 'mustfix' bugs for the release, and if this is listed I'll fix it. The silence can be masked :) Could we do some kind of collective RM for that relase? it's at least possible to do a release this way? Put up a list of tasks, another of bugs, vote and comment in what to do.. and simply do it.. Do we need a (benevolent) dictator for this? No, we need a benevolent worker :-) Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9816] New: - Programmatic Requests to JSP fail with Error Code 404
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=9816. 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=9816 Programmatic Requests to JSP fail with Error Code 404 Summary: Programmatic Requests to JSP fail with Error Code 404 Product: Tomcat 4 Version: 4.0.4 Beta 3 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello: If I try to access my JSP via a web browser, I have no problems. However, if I try to access the JSP programmatically, via HttpURLConnection, I get error 404 (as shown by the access logs). I know that there is a long standing bug in the 1.3 JDK related to HttpURLConnection (Java Bug #4160499), but the source of my problem is why Tomcat 4 returns status code 404 for a well-formed URL request. When my program runs, it constructs a URL of the form: http://localhost:8080/WebFoo/jsp/Folder1.jsp In my Java test program, I display the parts of the URL using the methods: url.getFile(), url.getHost(), etc. and it displays: URL Information for: http://localhost:8080/WebFoo/jsp/Folder1.jsp File: /WebFoo/jsp/Folder1.jsp Host: localhost Port: 8080 Protocol: http Ref: null Header Information: [1]: Content-Type: text/html [2]: Date: Wed, 12 Jun 2002 20:01:46 GMT [3]: Server: Apache Tomcat/4.0.4-b3 (HTTP/1.1 Connector) [4]: Connection: close conn.getHeaderField(0) returns HTTP/1.1 404 /jsp/Folder1.jsp status code = 404 As you can see, the header fields seems to indicate that my web application name (WebFoo) is lost somehow. The Tomcat 4 access log file records the entry: 127.0.0.1 - - [12/Jun/2002:15:50:08 -0500] GET /WebFoo/jsp/Folder1.jsp HTTP/1.1 404 627 Finally, my web application is not listed in the server.xml file as an explicit Context. Is this required? Can you help me to understand why I'm getting this 404 error code while things work fine my (IE) browser? Thanks, Glenn -- 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
kinman 2002/06/12 13:19:32
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
- The generated method should return a boolean, to indicate that the
rest of the page be skipped.
Revision ChangesPath
1.26 +21 -9
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.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- Generator.java11 Jun 2002 23:16:34 - 1.25
+++ Generator.java12 Jun 2002 20:19:32 - 1.26
@@ -462,6 +462,7 @@
private ServletWriter out;
private MethodsBuffer methodsBuffer;
+ private int methodNesting;
/**
* Constructor.
@@ -471,6 +472,7 @@
this.methodsBuffer = methodsBuffer;
handlerInfos = new Hashtable();
tagVarNumbers = new Hashtable();
+ methodNesting = 0;
}
/**
@@ -569,7 +571,7 @@
out.print (attributeValue(n.getPage(), false));
printParams(n);
out.println(););
- out.printil(return;);
+ out.printil((methodNesting 0)? return true;: return;);
out.popIndent();
out.printil(});
@@ -1013,14 +1015,18 @@
String tagMethod = _jspx_meth_ + baseVar;
// Generate a call to this method
- out.printin(tagMethod);
+ out.printin(if ();
+ out.print(tagMethod);
out.print(();
if (parent != null) {
out.print(parent);
out.print(, );
}
-// out.println(pageContext, _jspxState););
- out.println(pageContext););
+// out.println(pageContext, _jspxState));
+ out.println(pageContext)));
+ out.pushIndent();
+ out.printil((methodNesting 0)? return true;: return;);
+ out.popIndent();
// Set up new buffer for the method
outSave = out;
@@ -1028,10 +1034,11 @@
methodsBufferSave = methodsBuffer;
methodsBuffer = new MethodsBuffer();
+ methodNesting++;
// Generate code for method declaration
out.println();
out.pushIndent();
- out.printin(private void );
+ out.printin(private boolean );
out.print(tagMethod);
out.print(();
if (parent != null) {
@@ -1074,10 +1081,15 @@
if (n.isScriptless() varInfos == null
(tagVarInfos == null || tagVarInfos.length == 0)) {
// Generate end of method
+ if (methodNesting 0) {
+ out.printil(return false;);
+ }
out.popIndent();
out.printil(});
out.popIndent();
+ methodNesting--;
+
// Append any methods that got generated in the body to the
// current buffer
out.print(methodsBuffer.toString());
@@ -1319,7 +1331,7 @@
out.print(tagHandlerVar);
out.println(.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE));
out.pushIndent();
- out.printil(return;);
+ out.printil((methodNesting 0)? return true;: return;);
out.popIndent();
// TryCatchFinally
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jk 1.2 freese/snap time in JTC ?
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: 12 de junio de 2002 22:01 No, we need a benevolent worker :-) Just realized i was falling in my habitual naiveness.. :) The tasklist of the RM starts with collect open bugs, ok? We have the bugs reported by the query below in bugzilla, as opened bugs for JK, if anyone feels this lacks something.. feel free to add what you want.. http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDbug _status=NEWbug_status=ASSIGNEDbug_status=REOPENEDproduct=Tomcat+3pro duct=Tomcat+4component=Connector%3AJK%2FAJP+%28deprecated%29component= Connectors Adding the JNI problem reported by myself, could this be the list of actual open bugs against JK1.2.0? If yes, first task done...next please.. :) Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9816] - Programmatic Requests to JSP fail with Error Code 404
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=9816. 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=9816 Programmatic Requests to JSP fail with Error Code 404 --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 21:03 --- This problem looks to me like a programming error. Note: It's a particularity of Japser to only return the relative URL in the 404 (tested with Jasper 2, but Jasper 1 shouldn't be different). It could be considered a minor bug, I suppose. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6068] - AJP13 bad read, IOException
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=6068. 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=6068 AJP13 bad read, IOException [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 21:17 --- This has been fixed in the nightly builds. Please reopen if you still see this problem -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PROPOSAL] When Session Max reached, throw out oldest session
PROPOSAL: When Session Max reached, throw out oldest session Currently tomcat ships with the maximum number of sessions set to unlimited. They can expire by default after 30 minutes, however if too many sessions are created within the 30 minutes, you can run out of memory. To prevent running out of memory, you might choose to limit the allowed number of active sessions. If you use the default StanardManager (session manager) you can set the maxActiveSessions to effect a limit. However if you exceed the number of allowed sessions, a RuntimeException (IllegalStateException) is thrown. I propose two changes to reduce seeing these (IllegalStateException or OutOfMemory) exceptions for sessions; 1. When the maximum number of sessions is reached, change StandardManager from throwing an IllegalStateException exception, to expiring the Least Recently Used (LRUMap) session. 2. Instead of defaulting to an unlimited number of sessions (and getting visits from OutOfMemory), limit the number of sessions to 1 by default. [ ] Yes - make a patch [ ] No - Dont mess with sessions Cheers, -bob -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9816] - Programmatic Requests to JSP fail with Error Code 404
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=9816. 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=9816 Programmatic Requests to JSP fail with Error Code 404 --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 21:24 --- No, this shouldn't change anything. The request appears to get properly mapped to the context. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 build.properties.sample
remm2002/06/12 14:29:49
Modified:.build.properties.sample
Log:
- Update to MX4J 1.1.
Revision ChangesPath
1.44 +5 -5 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- build.properties.sample 12 Jun 2002 16:47:05 - 1.43
+++ build.properties.sample 12 Jun 2002 21:29:49 - 1.44
@@ -175,11 +175,11 @@
jdbc20ext.jar=${jdbc20ext.lib}/jdbc2_0-stdext.jar
-# - Java Management Extensions (JMX), JMX RI 1.0.1 or later or MX4J 1.0 or
later -
-jmx.home=${base.path}/mx4j-1.0b3
+# - Java Management Extensions (JMX), JMX RI 1.0.1 or later or MX4J 1.1 or
later -
+jmx.home=${base.path}/mx4j-1.1
jmx.lib=${jmx.home}/lib
-jmx.jar=${jmx.lib}/mx4j.jar
-jmx.loc=http://telia.dl.sourceforge.net/sourceforge/mx4j/mx4j-1.0b3.tar.gz
+jmx.jar=${jmx.lib}/mx4j-jmx.jar
+jmx.loc=http://telia.dl.sourceforge.net/sourceforge/mx4j/mx4j-1.1.tar.gz
# - Java Secure Sockets Extension (JSSE), version 1.0.2 or later -
--
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
kinman 2002/06/12 15:08:29
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
- If the page attribute for jsp:include or jsp:forward contains a '?',
then the separator after the page should be '' instead of '?'.
Revision ChangesPath
1.27 +24 -11
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.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- Generator.java12 Jun 2002 20:19:32 - 1.26
+++ Generator.java12 Jun 2002 22:08:28 - 1.27
@@ -507,26 +507,39 @@
*
* @param n the parent node for the param action nodes.
*/
- private void printParams(Node n) throws JasperException {
+ private void printParams(Node n, Node.JspAttribute page)
+ throws JasperException {
class ParamVisitor extends Node.Visitor {
- char separator = '?';
+ String separator;
+
+ ParamVisitor(String separator){
+ this.separator = separator;
+ }
public void visit(Node.ParamAction n) throws JasperException {
- out.print( + \);
+ out.print( + );
out.print(separator);
+ out.print( + \);
out.print(n.getAttributeValue(name));
out.print(=\ + );
out.print(attributeValue(n.getValue(), true));
// The separator is '' after the second use
- separator = '';
+ separator = \\;
}
}
+ String pValue = page.getValue();
+ String sep;
+ if (page.isExpression()) {
+ sep = (( + pValue + ).indexOf('?')0? '': '?');
+ } else {
+ sep = pValue.indexOf('?')0? \\: \?\;
+ }
if (n.getBody() != null) {
- n.getBody().visit(new ParamVisitor());
+ n.getBody().visit(new ParamVisitor(sep));
}
}
@@ -554,7 +567,7 @@
out.printin(JspRuntimeLibrary.include(request, response, );
out.print(attributeValue(n.getPage(), false));
- printParams(n);
+ printParams(n, n.getPage());
out.println(, out, + isFlush + ););
n.setEndJavaLine(out.getJavaLine());
@@ -568,8 +581,8 @@
out.printil(if (true) {); // So that javac won't complain about
out.pushIndent(); // codes after return
out.printin(pageContext.forward();
- out.print (attributeValue(n.getPage(), false));
- printParams(n);
+ out.print(attributeValue(n.getPage(), false));
+ printParams(n, n.getPage());
out.println(););
out.printil((methodNesting 0)? return true;: return;);
out.popIndent();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] Custom tag scripting variables
As discussed with Kin-Man, the following patch (for Jasper2)
addresses two issues related to scripting variables exposed by
custom tags (via TagExtraInfo class or TLD):
ISSUE 1:
+++
According to the JSP spec, scripting variables with scope AT_BEGIN
or AT_END are supposed to be visible from the begin element or end
element, respectively, of the custom tag that is exposing them, all
the way to the *end* of the page. This currently is not the case.
The attached patch addresses this problem by determining the AT_BEGIN
and AT_END scripting variables of any custom tag and declaring them as
local variables of the _jspService() method.
ISSUE 2:
+++
If a custom tag exposing scripting variables is nested inside
itself, its scripting variables get declared multiple times within the
same scope of the generated code, resulting in compilation
errors. This problem has been filed as bug #8926 (Synopsis: Duplicate
variable definition in generated Java source, related to custom tag
scripting variable).
The attached patch addresses this problem by declaring AT_BEGIN and
AT_END scripting variables once (as local variables of the
_jspService() method, see above), and declaring NESTED scripting
variables only at the outermost nesting level of their custom tag,
where nesting level corresponds the number of times the custom tag is
nested inside itself.
Example:
g:h
a:b -- nesting level 0, declares NESTED scripting variables
c:d
e:f
a:b -- nesting level 1, saves scripting variables
a:b -- nesting level 2, saves scripting variables
/a:b -- restores scripting variables
/a:b -- restores scripting variables
a:b -- nesting level 1, saves scripting variables
/a:b -- restores scripting variables
/e:f
/c:d
/a:b
a:b -- nesting level 0, does not declare any NESTED scripting variables
/a:b
/g:h
If a:b exposes any NESTED scripting variables, those variables are
going to be declared only once in the generated code, namely by the
*first* a:b at nesting level 0.
Any a:b with a nesting level 0 saves (in its begin element) the
current values of all its scripting variables to locale variables (named
for the scripting variable and the custom tag's nesting level) before
synchronizing the scripting variables as defined by the JSP spec. In
its end element, the custom tag restores the original values of the
scripting variables (that is, the values the scripting variables had when
the tag's begin element was encountered).
In addition, this patch stores a custom tag's scripting variables with
the custom tag itself, so the scripting variables don't need to be
determined over and over again.
This has resulted in two new accessor methods for Node.CustomTag:
public TagVariableInfo[] getTagVariableInfos()
public VariableInfo[] getVariableInfos()
Let me know if there are any problems with this patch.
Thanks,
Jan
Executing ssh-askpass to query the password...
Warning: Remote host denied X11 forwarding, perhaps xauth program could not be run on
the server side.
? build.properties
? build
? src/share/org/apache/jasper/compiler/Generator.java.SAVE
cvs server: Diffing .
cvs server: Diffing doc
cvs server: Diffing src
cvs server: Diffing src/bin
cvs server: Diffing src/share
cvs server: Diffing src/share/org
cvs server: Diffing src/share/org/apache
cvs server: Diffing src/share/org/apache/jasper
cvs server: Diffing src/share/org/apache/jasper/compiler
Index: src/share/org/apache/jasper/compiler/Generator.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.23
diff -u -r1.23 Generator.java
--- src/share/org/apache/jasper/compiler/Generator.java 10 Jun 2002 21:08:30 -
1.23
+++ src/share/org/apache/jasper/compiler/Generator.java 12 Jun 2002 21:49:23 -
@@ -184,13 +184,15 @@
*/
public void visit(Node.CustomTag n) throws JasperException {
+ // Create tag handler pool name and assign it to node
String name = createTagHandlerPoolName(n.getPrefix(),
- n.getShortName(),
- n.getAttributes());
+ n.getShortName(),
+ n.getAttributes());
n.setTagHandlerPoolName(name);
if (!names.contains(name)) {
names.add(name);
}
+
visitBody(n);
}
@@ -235,6 +237,80 @@
page.visit(new TagHandlerPoolVisitor(tagHandlerPoolNames));
}
+/*
+ * For every custom tag, declares its scripting variables with AT_BEGIN
+ * and AT_END scopes.
+ */
+private void
RE: cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0mod_jk.c
Thanks. I'll download an retest. Bojan On Thu, 2002-06-13 at 00:33, GOMEZ Henri wrote: This should fix the problem reported by Bojan. What about tagging jtc for jk_1_2_0 release ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 4:31 PM To: [EMAIL PROTECTED] Subject: cvs commit: jakarta-tomcat-connectors/jk/native/apache-2.0 mod_jk.c hgomez 2002/06/12 07:31:09 Modified:jk/native/apache-2.0 mod_jk.c Log: Fix the incorrect error reported when a worker is defined but didn't exist (reported by Bojan) Revision ChangesPath 1.45 +4 -1 jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c Index: mod_jk.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native/apache-2.0/mod_jk.c,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- mod_jk.c 8 May 2002 00:45:33 - 1.44 +++ mod_jk.c 12 Jun 2002 14:31:09 - 1.45 @@ -1324,6 +1324,9 @@ return OK;/* NOT r-status, even if it has changed. */ } } + else + return HTTP_INTERNAL_SERVER_ERROR; + } return DECLINED; -- 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] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 build.properties.sample
remm2002/06/12 16:04:57
Modified:.build.properties.sample
Log:
- Add PureTLS.
Revision ChangesPath
1.45 +7 -1 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- build.properties.sample 12 Jun 2002 21:29:49 - 1.44
+++ build.properties.sample 12 Jun 2002 23:04:57 - 1.45
@@ -214,6 +214,12 @@
nsis.loc=http://www.nullsoft.com/free/nsis/nsis198.exe
+# - PureTLS Extension, version 0.9 or later -
+puretls.home=${base.path}/puretls-0.9b2
+puretls.lib=${puretls.home}/build
+puretls.jar=${puretls.lib}/puretls.jar
+
+
# - Struts, version 1.0.1 or later -
struts.home=${base.path}/jakarta-struts-1.0.2
struts.lib=${struts.home}/lib
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina build.xml
remm2002/06/12 16:05:24
Modified:catalina build.xml
Log:
- Add PureTLS.
Revision ChangesPath
1.122 +2 -0 jakarta-tomcat-4.0/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/build.xml,v
retrieving revision 1.121
retrieving revision 1.122
diff -u -r1.121 -r1.122
--- build.xml 10 Jun 2002 05:27:44 - 1.121
+++ build.xml 12 Jun 2002 23:05:24 - 1.122
@@ -775,6 +775,8 @@
ant dir=${tomcat-util.home} target=build-main
property name=jmx.jar value=${jmx.jar} /
+ property name=puretls.jar value=${puretls.jar} /
+ property name=jsse.lib value=${jsse.lib} /
/ant
copy todir=${catalina.build}/server/lib
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2 build.xml
costin 2002/06/12 16:15:27
Modified:jasper2 build.xml
Log:
Build the jars during build, copy in deploy.
Revision ChangesPath
1.7 +31 -23jakarta-tomcat-jasper/jasper2/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.xml 6 Jun 2002 00:23:35 - 1.6
+++ build.xml 12 Jun 2002 23:15:27 - 1.7
@@ -92,6 +92,31 @@
/fileset
/copy
+ !-- Jasper Compiler JAR File --
+ jar jarfile=${jasper.build}/shared/lib/jasper-compiler.jar
+ fileset dir=${jasper.build}/shared/classes
+include name=org/apache/jasper/compiler/** /
+include name=org/apache/jasper/xmlparser/** /
+include name=org/apache/jasper/servlet/** /
+exclude name=org/apache/jasper/Constants.class /
+exclude name=org/apache/jasper/JasperException.class /
+include name=org/apache/jasper/*.class /
+ /fileset
+/jar
+
+!-- Jasper Runtime JAR File --
+jar jarfile=${jasper.build}/shared/lib/jasper-runtime.jar
+ fileset dir=${jasper.build}/shared/classes
+include name=org/apache/jasper/Constants.class /
+include name=org/apache/jasper/JasperException.class /
+include name=org/apache/jasper/logging/** /
+include name=org/apache/jasper/resources/** /
+include name=org/apache/jasper/runtime/** /
+include name=org/apache/jasper/util/** /
+ /fileset
+/jar
+
+
/target
@@ -178,30 +203,13 @@
!-- == DEPLOY: Create Jasper JARs == --
target name=deploy depends=deploy-static,build-main
description=Build and deploy Jasper component
-
- !-- Jasper Compiler JAR File --
- jar jarfile=${jasper.deploy}/common/lib/jasper-compiler.jar
- fileset dir=${jasper.build}/shared/classes
-include name=org/apache/jasper/compiler/** /
-include name=org/apache/jasper/xmlparser/** /
-include name=org/apache/jasper/servlet/** /
-exclude name=org/apache/jasper/Constants.class /
-exclude name=org/apache/jasper/JasperException.class /
-include name=org/apache/jasper/*.class /
- /fileset
-/jar
+echo message=Deploy to ${jasper.deploy}/common/lib /
+!-- Jasper Compiler JAR File --
+copy file=${jasper.build}/shared/lib/jasper-compiler.jar
+ tofile=${jasper.deploy}/common/lib/jasper-compiler.jar /
-!-- Jasper Runtime JAR File --
-jar jarfile=${jasper.deploy}/common/lib/jasper-runtime.jar
- fileset dir=${jasper.build}/shared/classes
-include name=org/apache/jasper/Constants.class /
-include name=org/apache/jasper/JasperException.class /
-include name=org/apache/jasper/logging/** /
-include name=org/apache/jasper/resources/** /
-include name=org/apache/jasper/runtime/** /
-include name=org/apache/jasper/util/** /
- /fileset
-/jar
+copy file=${jasper.build}/shared/lib/jasper-runtime.jar
+ tofile=${jasper.deploy}/common/lib/jasper-runtime.jar /
!-- Copy Ant JAR --
copy todir=${jasper.deploy}/common/lib file=${ant.jar}/
--
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
costin 2002/06/12 16:17:36
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
pageContext.getRequest() returns a ServletRequest, not HttpServletRequest.
Revision ChangesPath
1.28 +4 -4
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.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- Generator.java12 Jun 2002 22:08:28 - 1.27
+++ Generator.java12 Jun 2002 23:17:36 - 1.28
@@ -1071,7 +1071,7 @@
out.println(ServletContext application =
pageContext.getServletContext(););
}
if (n.isHasUsebean() || n.isHasIncludeAction() ||
n.isHasSetProperty()) {
- out.println(HttpServletRequest request =
pageContext.getRequest(););
+ out.println(HttpServletRequest request =
(HttpServletRequest)pageContext.getRequest(););
}
if (n.isHasIncludeAction()) {
out.println(ServletResponse response =
pageContext.getResponse(););
--
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 EmbededServletOptions.java
costin 2002/06/12 16:18:50 Modified:jasper2/src/share/org/apache/jasper EmbededServletOptions.java Log: Turn class debug info, they are quite usefull in debugging and don't hurt anyone. Revision ChangesPath 1.6 +4 -4 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/EmbededServletOptions.java Index: EmbededServletOptions.java === RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/EmbededServletOptions.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- EmbededServletOptions.java31 May 2002 05:13:13 - 1.5 +++ EmbededServletOptions.java12 Jun 2002 23:18:50 - 1.6 @@ -114,7 +114,7 @@ /** * Do we want to include debugging information in the class file? */ -public boolean classDebugInfo = false; +public boolean classDebugInfo = true; /** * Background compile thread check interval in seconds. -- 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 JspC.java
costin 2002/06/12 16:20:15
Modified:jasper2/src/share/org/apache/jasper JspC.java
Log:
A bit more verbose error message, from some reasons the stack trace
never shows up and is hard to guess what's going on.
BTW, it seems the classes are compiled automatically - that's a change
in behavior.
Revision ChangesPath
1.7 +5 -4
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java
Index: JspC.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/JspC.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- JspC.java 2 Jun 2002 21:40:22 - 1.6
+++ JspC.java 12 Jun 2002 23:20:15 - 1.7
@@ -470,7 +470,8 @@
}
return true;
} catch (JasperException je) {
-//je.printStackTrace(log);
+System.out.println(Error compiling + file );
+je.printStackTrace();
Constants.message(jspc.error.jasperException,
new Object[] {file, je}, Logger.ERROR);
if (dieLevel != NO_DIE_LEVEL) {
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/jni jkjni.dsp
nacho 2002/06/12 16:26:36 Modified:jk/native2/server/isapi isapi.dsp jk/native2/server/apache2 mod_jk2.dsp jk/native2/jni jkjni.dsp Log: * Added jk_user and jk_signal to the win32 build Revision ChangesPath 1.16 +20 -12jakarta-tomcat-connectors/jk/native2/server/isapi/isapi.dsp Index: isapi.dsp === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/isapi/isapi.dsp,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- isapi.dsp 9 Jun 2002 01:52:34 - 1.15 +++ isapi.dsp 12 Jun 2002 23:26:35 - 1.16 @@ -157,10 +157,6 @@ # End Source File # Begin Source File -SOURCE=..\..\common\jk_logger_win32_message.h -# End Source File -# Begin Source File - SOURCE=..\..\common\jk_map.c # End Source File # Begin Source File @@ -205,10 +201,6 @@ # End Source File # Begin Source File -SOURCE=..\..\common\jk_registry.h -# End Source File -# Begin Source File - SOURCE=..\..\common\jk_requtil.c # End Source File # Begin Source File @@ -221,6 +213,10 @@ # End Source File # Begin Source File +SOURCE=..\..\common\jk_signal.c +# End Source File +# Begin Source File + SOURCE=..\..\common\jk_uriEnv.c # End Source File # Begin Source File @@ -229,6 +225,10 @@ # End Source File # Begin Source File +SOURCE=..\..\common\jk_user.c +# End Source File +# Begin Source File + SOURCE=..\..\common\jk_vm_default.c # End Source File # Begin Source File @@ -255,10 +255,6 @@ SOURCE=..\..\common\jk_workerEnv.c # End Source File -# Begin Source File - -SOURCE=..\..\jni\org_apache_jk_apr_AprImpl.h -# End Source File # End Group # Begin Group Header Files @@ -297,6 +293,10 @@ # End Source File # Begin Source File +SOURCE=..\..\common\jk_logger_win32_message.h +# End Source File +# Begin Source File + SOURCE=..\..\include\jk_map.h # End Source File # Begin Source File @@ -321,6 +321,10 @@ # End Source File # Begin Source File +SOURCE=..\..\common\jk_registry.h +# End Source File +# Begin Source File + SOURCE=..\..\include\jk_requtil.h # End Source File # Begin Source File @@ -350,6 +354,10 @@ # Begin Source File SOURCE=..\..\include\jk_workerEnv.h +# End Source File +# Begin Source File + +SOURCE=..\..\jni\org_apache_jk_apr_AprImpl.h # End Source File # End Group # Begin Group Resource Files 1.3 +12 -0 jakarta-tomcat-connectors/jk/native2/server/apache2/mod_jk2.dsp Index: mod_jk2.dsp === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/server/apache2/mod_jk2.dsp,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- mod_jk2.dsp 9 Jun 2002 01:53:50 - 1.2 +++ mod_jk2.dsp 12 Jun 2002 23:26:35 - 1.3 @@ -141,6 +141,10 @@ # End Source File # Begin Source File +SOURCE=..\..\jni\jk_jni_aprImpl.c +# End Source File +# Begin Source File + SOURCE=.\jk_logger_apache2.c # End Source File # Begin Source File @@ -213,11 +217,19 @@ # End Source File # Begin Source File +SOURCE=..\..\common\jk_signal.c +# End Source File +# Begin Source File + SOURCE=..\..\common\jk_uriEnv.c # End Source File # Begin Source File SOURCE=..\..\common\jk_uriMap.c +# End Source File +# Begin Source File + +SOURCE=..\..\common\jk_user.c # End Source File # Begin Source File 1.3 +8 -0 jakarta-tomcat-connectors/jk/native2/jni/jkjni.dsp Index: jkjni.dsp === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/jni/jkjni.dsp,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jkjni.dsp 9 Jun 2002 01:54:07 - 1.2 +++ jkjni.dsp 12 Jun 2002 23:26:36 - 1.3 @@ -200,11 +200,19 @@ # End Source File # Begin Source File +SOURCE=..\common\jk_signal.c +# End Source File +# Begin Source File + SOURCE=..\common\jk_uriEnv.c # End Source File # Begin Source File SOURCE=..\common\jk_uriMap.c +# End Source File +# Begin Source File + +SOURCE=..\common\jk_user.c # End Source File # Begin Source File -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PATCH] improved HTMLManagerServlet
Glenn Nielsen wrote: I installed this and took a look at it. Looking much better. :-) Here are some more suggestions for improvement. 1. Change the title to Tomcat Web Application Manager. done 2. Move the Message: table to just below the page title. done 3. Only enable the Start/Stop/Reload links based on the status of the web application. i.e. A web application that is currently stopped can only be started or removed. done 4. Include the hostname and port somewhere, perhaps below the title. The hostname and port is in the browser's address field, do you want it anyway? 5. Add Help/Documentation for the different options. What do you have in mind, listing help in the Message: table? 6. There are some features of the manager which are not available /manager/resources /manager/roles /manager/sessions. sessions is already available in link, I will attempt resources and roles later. Regards, Glenn Work has been busy, so I have been a little slow getting these mods done. Regards Malcolm _ Chat with friends online, try MSN Messenger: http://messenger.msn.com /* * $Header: /home/cvspublic/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/HTMLManagerServlet.java,v 1.7 2002/06/10 19:19:23 glenn Exp $ * $Revision: 1.7 $ * $Date: 2002/06/10 19:19:23 $ * * * * The Apache Software License, Version 1.1 * * Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright *notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright *notice, this list of conditions and the following disclaimer in *the documentation and/or other materials provided with the *distribution. * * 3. The end-user documentation included with the redistribution, if *any, must include the following acknowlegement: * This product includes software developed by the *Apache Software Foundation (http://www.apache.org/). *Alternately, this acknowlegement may appear in the software itself, *if and wherever such third-party acknowlegements normally appear. * * 4. The names The Jakarta Project, Tomcat, and Apache Software *Foundation must not be used to endorse or promote products derived *from this software without prior written permission. For written *permission, please contact [EMAIL PROTECTED] * * 5. Products derived from this software may not be called Apache *nor may Apache appear in their names without prior written *permission of the Apache Group. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * http://www.apache.org/. * * [Additional notices, if required by prior licensing conditions] * */ package org.apache.catalina.servlets; import java.io.IOException; import java.io.PrintWriter; import java.io.StringWriter; import java.text.MessageFormat; import java.util.Date; import java.util.Iterator; import java.util.Map; import java.util.TreeMap; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import org.apache.catalina.Context; import org.apache.catalina.util.ServerInfo; /** * Servlet that enables remote management of the web applications installed * within the same virtual host as this web application is. Normally, this * functionality will be protected by a security constraint in the web * application deployment descriptor. However, this requirement can be * relaxed during testing. * p * The difference between this codeManagerServlet/code and this * Servlet is that this Servlet prints out a HTML interface which * makes it easier to
DO NOT REPLY [Bug 9677] - JSP files not recompiled when newer
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=9677. 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=9677 JSP files not recompiled when newer [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9722] - java.lang.ClassCastException: org.apache.catalina.connector.HttpRequestFacade
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=9722. 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=9722 java.lang.ClassCastException: org.apache.catalina.connector.HttpRequestFacade [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 23:47 --- The patch has been applied in the 4.1.4 milestone. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9700] - JNDIRealm authentication incorrectly succeeds with blank password
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=9700. 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=9700 JNDIRealm authentication incorrectly succeeds with blank password [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-06-12 23:49 --- The patch has been applied, and will be integrated in the 4.1.5 milestone. -- 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/06/12 17:06:37 Modified:.RELEASE-NOTES-4.1.txt Log: - Update release notes. Revision ChangesPath 1.9 +34 -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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- RELEASE-NOTES-4.1.txt 10 Jun 2002 01:47:52 - 1.8 +++ RELEASE-NOTES-4.1.txt 13 Jun 2002 00:06:37 - 1.9 @@ -64,6 +64,9 @@ [4.1.4] MBeanUtils: Allow specifying custom MBean descriptor files. +[4.1.5] ServerLifecycleListener: +Generate MBeans for the JNDI resources of the contexts. + --- Jasper New Features: @@ -231,6 +234,23 @@ WebappLoader: Use introspection to instantiate the class loader. +[4.1.4] #9722 +java.lang.ClassCastException: +org.apache.catalina.connector.HttpRequestFacade +ApplicationDispatcher: +The check to unwrap must also handle facades. + +[4.1.5] #9700 +JNDIRealm authentication incorrectly succeeds with blank password +JNDIRealm: +The security exploit has been fixed. + +[4.1.5] ProxyDirContext: +Use a LRUMap instead of an unbounded hashtable for the cache. + +[4.1.5] HTMLManagerServlet: +Many improvements and small feature additions. + Jasper Bug Fixes: @@ -269,6 +289,19 @@ [4.1.3] Generator: Fix spec compliance bug where a tag could define scripting variables in both the TLD and the TagExtraInfo class. + +[4.1.5] Generator: +Code cleanup, removing the need for a state object. + +[4.1.5] Generator: +Fix bugs introduced with buffer reuse. + +[4.1.5] Generator: +Fix bug when specifying a redirect which already included part of a +quesry string. + +[4.1.5] Compiler: +Clean up Ant error message generation. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-NOTES-4.0-B1.txt RELEASE-NOTES-4.0-B2.txt RELEASE-NOTES-4.0-B3.txt RELEASE-NOTES-4.0-B4.txt RELEASE-NOTES-4.0-B5.txt RELEASE-NOTES-4.0-B6.txt RELEASE-NOTES-4.0-B7.txt RELEASE-NOTES-4.0-RC1.txt RELEASE-NOTES-4.0-RC2.txt RELEASE-NOTES-4.0.txt RELEASE-NOTES-4.1-dev.txt RELEASE-NOTES-4.1.0.txt RELEASE-PLAN-4.0.txt
remm2002/06/12 17:10:14 Removed: .RELEASE-NOTES-4.0-B1.txt RELEASE-NOTES-4.0-B2.txt RELEASE-NOTES-4.0-B3.txt RELEASE-NOTES-4.0-B4.txt RELEASE-NOTES-4.0-B5.txt RELEASE-NOTES-4.0-B6.txt RELEASE-NOTES-4.0-B7.txt RELEASE-NOTES-4.0-RC1.txt RELEASE-NOTES-4.0-RC2.txt RELEASE-NOTES-4.0.txt RELEASE-NOTES-4.1-dev.txt RELEASE-NOTES-4.1.0.txt RELEASE-PLAN-4.0.txt Log: - Remove documents related to Tomcat 4.0.x (they exist in the 4.0 branch). -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] webapps/{manager,admin}/WEB-INF/web.xml: display-name and description
Now that we can SEE all the contexts' display-names (thanks to Malcolm's much-improved HTMLServlet), these two webapps should have display-name elements (so should the examples, but this is a start). --- webapps/admin/WEB-INF/web.xml.orig Tue May 7 12:33:44 2002 +++ webapps/admin/WEB-INF/web.xml Wed Jun 12 20:01:30 2002 @@ -6,6 +6,12 @@ web-app + display-nameTomcat Administration Application/display-name + description +A full-blown web-based Administration Console +for the Tomcat Web Server. + /description + !-- Action Servlet Configuration -- servlet servlet-nameaction/servlet-name --- webapps/manager/WEB-INF/web.xml.orig Wed Jun 12 20:00:07 2002 +++ webapps/manager/WEB-INF/web.xml Wed Jun 12 20:01:03 2002 @@ -6,6 +6,12 @@ web-app + display-nameTomcat Manager Application/display-name + description +A simpler web-based application for the Tomcat Web Server; + Manager lets you view, load/unload/etc particular web applications. + /description + !-- Define the Manager Servlet Change servlet-class to: org.apache.catalina.servlets.HTMLManagerServlet to get a Servlet with a more intuitive HTML interface, don't change if you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 build.xml tomcat.nsi
remm2002/06/12 17:21:36
Modified:.build.xml tomcat.nsi
Log:
- The installer will now display the full version number of Tomcat, as defined in
the build.properties.
Revision ChangesPath
1.73 +3 -1 jakarta-tomcat-4.0/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -r1.72 -r1.73
--- build.xml 12 Jun 2002 16:47:05 - 1.72
+++ build.xml 13 Jun 2002 00:21:36 - 1.73
@@ -261,7 +261,9 @@
todir=${tomcat.dist} /
copy file=${javaservice.home}/bin/JavaService.exe
tofile=${tomcat.dist}/bin/tomcat.exe /
-copy file=tomcat.nsi tofile=${tomcat.dist}/tomcat.nsi /
+filter token=VERSION value=${version}/
+copy file=tomcat.nsi tofile=${tomcat.dist}/tomcat.nsi
+ filtering=true/
exec dir=${tomcat.dist} executable=${nsis.home}\makensis-bz2.exe
arg value=tomcat.nsi /
/exec
1.32 +2 -2 jakarta-tomcat-4.0/tomcat.nsi
Index: tomcat.nsi
===
RCS file: /home/cvs/jakarta-tomcat-4.0/tomcat.nsi,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- tomcat.nsi11 Jun 2002 00:27:56 - 1.31
+++ tomcat.nsi13 Jun 2002 00:21:36 - 1.32
@@ -3,7 +3,7 @@
; $Id$
Name apache-tomcat-4.1
-Caption Apache Tomcat 4.1
+Caption Apache Tomcat @VERSION@
OutFile tomcat4.exe
CRCCheck on
SetCompress force
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina build.xml
remm2002/06/12 17:22:21
Modified:catalina build.xml
Log:
- Add Ant on the classpath (removes lots of errors when generating the
Javadocs).
Revision ChangesPath
1.123 +3 -0 jakarta-tomcat-4.0/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/build.xml,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -r1.122 -r1.123
--- build.xml 12 Jun 2002 23:05:24 - 1.122
+++ build.xml 13 Jun 2002 00:22:21 - 1.123
@@ -27,6 +27,7 @@
property name=tomcat-http11.home value=${jtc.home}/http11/
!-- Dependent JARs and files --
+ property name=ant.jar value=${ant.home}/lib/ant.jar/
property name=tomcat-util.jar
value=${tomcat-util.home}/build/lib/tomcat-util.jar/
property name=tomcat-coyote.jar
@@ -47,6 +48,7 @@
!-- Construct Catalina classpath --
path id=catalina.classpath
pathelement location=${activation.jar}/
+pathelement location=${ant.jar}/
pathelement location=${commons-beanutils.jar}/
pathelement location=${commons-collections.jar}/
pathelement location=${commons-daemon.jar}/
@@ -79,6 +81,7 @@
path id=test.classpath
pathelement location=${junit.jar}/
pathelement location=${activation.jar}/
+pathelement location=${ant.jar}/
pathelement location=${commons-beanutils.jar}/
pathelement location=${commons-collections.jar}/
pathelement location=${commons-daemon.jar}/
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PROPOSAL] When Session Max reached, throw out oldest session
[EMAIL PROTECTED] wrote: PROPOSAL: When Session Max reached, throw out oldest session Currently tomcat ships with the maximum number of sessions set to unlimited. They can expire by default after 30 minutes, however if too many sessions are created within the 30 minutes, you can run out of memory. To prevent running out of memory, you might choose to limit the allowed number of active sessions. If you use the default StanardManager (session manager) you can set the maxActiveSessions to effect a limit. However if you exceed the number of allowed sessions, a RuntimeException (IllegalStateException) is thrown. I propose two changes to reduce seeing these (IllegalStateException or OutOfMemory) exceptions for sessions; 1. When the maximum number of sessions is reached, change StandardManager from throwing an IllegalStateException exception, to expiring the Least Recently Used (LRUMap) session. The session manager definitely needs to go through a refactoring, and this is a good start. This behavior seems better to me, esp since it is possible to disable it (by setting maxActiveSessions to -1). 2. Instead of defaulting to an unlimited number of sessions (and getting visits from OutOfMemory), limit the number of sessions to 1 by default. Going with an upper bound seems better for reliability in the default configuration. +1. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: JNDI with a custom factory not working
On June 12, 2002 07:45 am, Arshad Mahmood wrote: I am having a problem trying to use a custom factory with JNDI. I get an exception froom org.apache.naming.factory.ResourceFactory. I have added debug and it appears that my factory parameter is not being picked up from the server.xml. Can somebody familiar with the naming code point me to the classes I need to look at to trace this problem. Alternatively, if somebody can confirm that the JNDI-Howto example for a custom beanFactory works correctly in 4.1 (I have tried it and it doesn't) then I will look at my configuration again. Doesn't work for me either. Inserting a listBindings() call for java:comp/env/bean reveals nothing bound there. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Jasper2: jspc and JspCompilationContext
There are few bugs in jspc, mostly related with the generation of the class name and the mangling. It seems CommandLineCtx and JspEngineContext are almost completely duplicated. I did a small change and turned JspCompilationContext into an abstract class, with all the code from JspEngineContext that deals with marshalling ( and is duplicated in CLCtx ). The abstract methods are those dealing with class loader and with getting resources. Is it ok to commit it ? Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Small help
Isn't the Java Groups JAR available as a separate JAR at www.javagroups.org Put the JAR in your tomcat/common/lib and try it out. Anand -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 5:31 PM To: [EMAIL PROTECTED] Subject: Small help Hi all, I have a small problem. I am trying out Session Replication in Tomcat 4.0.3. But it does not work. In the site theserver.com there was a detailed step by step installation procedure. I tried out that but it still does not work. They had mentioned 2 test programs to try out if it did not work java org.javagroups.tests.McastReceiverTest -mcast_addr 224.10.10.10 -port . Then start McastSenderTest: java org.javagroups.tests.McastSenderTest -mcast_addr 224.10.10.10 -port . But these 2 are not present in the jar files. Anybody has a clue With Best Regards Jagan K Samuel With Best Regards Jagan K Samuel -- 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]
Help..Tomcat4x+jdk1.3+FreeBSD..Hang Why...
hi I installed the linux-jdk1.3 and linux-ibm-jdk1.3.1 using ports in the FreeBSD. When i tried to run tomcat4+with mentioned JVM machine gets hang...Below is some of the parameter which i tried .. Os Jdk TomcatRun/Or Not FreeBSD Sun1.2 4xYes FreeBSD Sun1.3 4xNo(HotSpot Error Unable to Find Pid) ..Why??? FreeBSD Sun1.4 4xNo(HotSpot Error Unable to Find Pid) ..Why??? FreeBSD IBM1.3 4xHang..Why ??? FreeBSD IBM1.3.1 4xHang..Why??? Windows98 IBM1.3 4xRun Windows98 IBM1.3.1 4xRun FreeBSD Sun1.2 3xRun FreeBSD Sun1.3 3xRun FreeBSD Sun1.3.1 3xRun FreeBSD Sun1.4 3xRun FreeBSD IBM1.3 3xRun FreeBSD IBM1.3.1 3xRun 4x:-Tomcat 4.0.1 and Tomcat4.0.3 FreeBSD4.5 Release + Linux_base6 Is there any problem with Tomcat4 or FreeBSD . Tomcat4 runs successfuly even in windows98... Can any body provide me any suggestion Can anybody tell me whos are the developers of tomcat4x Bye Sonam __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 6457] - mod_jk causes segmentation fault with JkLogLevel != debug
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=6457. 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=6457 mod_jk causes segmentation fault with JkLogLevel != debug --- Additional Comments From [EMAIL PROTECTED] 2002-06-13 06:03 --- Can you send a stack trace ( gdb httpd core, then bt ) ? This is most likely due to a printf(%s) with null argument, jk2 has replaced all calls to APR equivalent. I'll do a search on the source and check the log statements. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
