cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_jni.c
mturk 2002/10/13 23:29:53 Modified:jk/native2/common jk_worker_jni.c Log: Change the onShutdown worker from disabled to lb_disabled Revision ChangesPath 1.30 +1 -1 jakarta-tomcat-connectors/jk/native2/common/jk_worker_jni.c Index: jk_worker_jni.c === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worker_jni.c,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- jk_worker_jni.c 3 Oct 2002 01:33:15 - 1.29 +++ jk_worker_jni.c 14 Oct 2002 06:29:53 - 1.30 @@ -366,7 +366,7 @@ */ env-l-jkLog(env, env-l, JK_LOG_INFO, jni.init() disabling the non init hook worker\n); -_this-mbean-disabled = 1; +_this-lb_disabled = JK_TRUE; } #if 0 vm-detach(env, vm); -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c
mturk 2002/10/13 23:30:42
Modified:jk/native2/common jk_worker_lb.c
Log:
Check if the worker has lb_disabled flag set, and behave like it was
disabled.
Revision ChangesPath
1.26 +3 -0 jakarta-tomcat-connectors/jk/native2/common/jk_worker_lb.c
Index: jk_worker_lb.c
===
RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/common/jk_worker_lb.c,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- jk_worker_lb.c3 Oct 2002 01:33:15 - 1.25
+++ jk_worker_lb.c14 Oct 2002 06:30:42 - 1.26
@@ -143,6 +143,7 @@
if( w-mbean-disabled ) continue;
if( w-in_error_state ) continue;
+if( w-lb_disabled ) continue;
if( rc==NULL ) {
rc=w;
@@ -182,6 +183,7 @@
jk_worker_t *w=lb-workerTables[level][i];
if( w-mbean-disabled ) continue;
+if( w-lb_disabled ) continue;
if(w-in_error_state) {
/* Check if it's ready for recovery */
@@ -221,6 +223,7 @@
jk_worker_t *w=lb-workerTables[level][i];
if( w-mbean-disabled == JK_TRUE ) continue;
+if( w-lb_disabled ) continue;
error_workers++;
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/native2/include jk_worker.h
mturk 2002/10/13 23:32:50 Modified:jk/native2/include jk_worker.h Log: Add the lb_disabled flag, that when set marks the worker out from the lb scheme. This is used for non-channel workers that doesnt participate in the TC connections. These flag is set inside the particular worker implementation. Revision ChangesPath 1.27 +5 -1 jakarta-tomcat-connectors/jk/native2/include/jk_worker.h Index: jk_worker.h === RCS file: /home/cvs/jakarta-tomcat-connectors/jk/native2/include/jk_worker.h,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- jk_worker.h 29 Jun 2002 18:33:06 - 1.26 +++ jk_worker.h 14 Oct 2002 06:32:49 - 1.27 @@ -188,6 +188,10 @@ */ int lb_factor; int lb_value; +/* If set then the worker doesn't participate in the + * load-balancer scheme. This is used for non-Tomcat workers. + */ +int lb_disabled; /* Time when the last error occured on this worker */ time_t error_time; -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13578] - Fix for JSP disclosure bug for all 4.0-4.0.5, 4.1-4.1.11 releases
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=13578. 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=13578 Fix for JSP disclosure bug for all 4.0-4.0.5, 4.1-4.1.11 releases [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 07:05 --- Sorry, but this has nothing to do in bugzilla, which is for reporting *BUGS*, not unsupported workarounds for security holes. Please post this wherever it is appropriate (tomcat-user or something). This is not a judgement on the quality of your work, or the benefit or having additional workarounds to the security hole. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13194] - refreshing JSP containing a body tag gives problem on alternate refresh
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=13194. 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=13194 refreshing JSP containing a body tag gives problem on alternate refresh --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:03 --- Agree, appears to not be calling release() method. Attempted with a custom iteration tag of mine; tag only runs once. If I forcably reset the iterator to the beginning of the list in doStartTag then it works; otherwise it appears the iterator is not reset and we remain at the end of the list when running the tag again. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13570] - tag pooling not working
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=13570. 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=13570 tag pooling not working --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:04 --- Doesn't call release() method also reference in bug 13194. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13538] - Cannot set relative path in %@include ... %directive
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=13538. 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=13538 Cannot set relative path in %@include ... %directive [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:09 --- I cannot reproduce this. Please attach a test case. Based on the include example, this works with the current CVS code (no relevant fixes appear to have been made, but I could be wrong): pIn place evaluation of another JSP which gives you the current time: %@ include file=../a/foo.jsp % p jsp:include page=/a/foo.html flush=true/ by including the output of another JSP: jsp:include page=../a/foo.jsp flush=true/ (this is in folder /b in the context, and a folder /a with foo.jsp exists) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13583] - Relative includes/forwards with ../s broken
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=13583. 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=13583 Relative includes/forwards with ../s broken [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |Normal --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:11 --- Are you trying to use .. in a path from a servlet ? This is not particularly useful as you have to produce an aboslute URL, but I can see why it's not working looking at the code. I cannot reproduce bug 13538, but this is a different issue. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13570] - tag pooling not working
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=13570. 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=13570 tag pooling not working [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:13 --- *** This bug has been marked as a duplicate of 13392 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13392] - When tag pooling is enabled, release() is not called on tag instances
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=13392. 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=13392 When tag pooling is enabled, release() is not called on tag instances [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:13 --- *** Bug 13570 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13194] - refreshing JSP containing a body tag gives problem on alternate refresh
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=13194. 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=13194 refreshing JSP containing a body tag gives problem on alternate refresh [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:14 --- This other bug contains a detailed explanation. *** This bug has been marked as a duplicate of 13392 *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13392] - When tag pooling is enabled, release() is not called on tag instances
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=13392. 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=13392 When tag pooling is enabled, release() is not called on tag instances [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 08:14 --- *** Bug 13194 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.xml
remm2002/10/14 02:25:08
Modified:.build.xml
Log:
- Should fix release target.
Revision ChangesPath
1.43 +6 -6 jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- build.xml 11 Oct 2002 19:31:58 - 1.42
+++ build.xml 14 Oct 2002 09:25:08 - 1.43
@@ -418,7 +418,7 @@
!-- RELEASE: Create Release === --
- target name=release
depends=prepare-release,clean,dist,dist-source,installer,package-zip,package-tgz,package-src-zip,package-src-tgz,win32-release
+ target name=release
depends=prepare-release,clean,dist,dist-source,installer,package-zip,package-tgz,package-src-zip,package-src-tgz
description=Create a Tomcat 5 packaged distribution
mkdir dir=${tomcat.release}/
@@ -426,6 +426,11 @@
mkdir dir=${tomcat.release}/v${version}/bin/
mkdir dir=${tomcat.release}/v${version}/src/
+copy file=${tomcat.dist}/${final.name}.exe
+ todir=${tomcat.release}/v${version}/bin
+ failonerror=false/
+delete file=${tomcat.dist}/${final.name}.exe
+ failonerror=false/
move file=${tomcat.dist}/${final.name}.tar.gz
todir=${tomcat.release}/v${version}/bin/
move file=${tomcat.dist}/${final.name}.zip
@@ -451,11 +456,6 @@
copy file=resources/welcome.bin.html
tofile=${tomcat.release}/v${version}/bin/README.html
filtering=true/
- /target
-
- target name=win32-release if=execute.installer
-move file=${tomcat.dist}/${final.name}.exe
- todir=${tomcat.release}/v${version}/bin/
/target
target name=package-zip
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13583] - Relative includes/forwards with ../s broken
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=13583. 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=13583 Relative includes/forwards with ../s broken --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 09:44 --- I'm using this in a JSP page as follows: jsp:forward page=../fragments/container_content.jsp/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13538] - Cannot set relative path in %@include ... %directive
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=13538. 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=13538 Cannot set relative path in %@include ... %directive [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 09:50 --- *** Bug 13583 has been marked as a duplicate of this bug. *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13595] New: - Tomcat doesn't start when examples aren't installed
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=13595. 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=13595 Tomcat doesn't start when examples aren't installed Summary: Tomcat doesn't start when examples aren't installed Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi, I installed Tomcat without the examples. If I try to start Tomcat, I get the following error in the logs: Created catalinaLoader in: C:\Program Files\Apache Group\Tomcat 4.1\server\lib 14-okt-2002 13:25:13 org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information 14-okt-2002 13:25:13 org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance 14-okt-2002 13:25:14 org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer 14-okt-2002 13:25:16 org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.BootstrapService.start (BootstrapService.java:245) at org.apache.catalina.startup.BootstrapService.main (BootstrapService.java:307) Caused by: java.lang.IllegalArgumentException: Document base C:\Program Files\Apache Group\Tomcat 4.1\webapps\examples does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase (FileDirContext.java:193) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3397) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start (StandardEngine.java:347) at org.apache.catalina.core.StandardService.start (StandardService.java:497) at org.apache.catalina.core.StandardServer.start (StandardServer.java:2189) at org.apache.catalina.startup.CatalinaService.start (CatalinaService.java:271) ... 6 more If I manually create the examples dir, Tomcat starts normally... I'm using: - Windows XP - JDK 1.4.1 - Tomcate 4.1.12 LITE -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13595] - Tomcat doesn't start when examples aren't installed
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=13595. 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=13595 Tomcat doesn't start when examples aren't installed [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 11:34 --- This has been reported already, and will now be reported as a warning in the next release. BTW, the easiest solution is to remove the examples webapp declaration in server.xml. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13597] New: - ClassCastException in jsp:setProperty if editor class set in BeanInfo
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=13597.
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=13597
ClassCastException in jsp:setProperty if editor class set in BeanInfo
Summary: ClassCastException in jsp:setProperty if editor class
set in BeanInfo
Product: Tomcat 4
Version: 4.0.1 Final
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Minor
Priority: Other
Component: Jasper
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
description : FULL PRODUCT VERSION :
java version 1.4.1
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)
Java 2 Enterprise Edition version 1.3.1, build 1.3.1-b17
FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Apache Tomcat/4.0.1
Sun ONE Studio 4.0 update 1
A DESCRIPTION OF THE PROBLEM :
When an editor class is set to the property in the
BeanInfo, the jsp tag setProperty throw a
ClassCastException.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. execute the given web application
2. Go to URL http://localhost:8081/webapp/login.jsp
3. type the username toto
4. type enter.
5. you should see the exception
EXPECTED VERSUS ACTUAL BEHAVIOR :
Expected result:
Welcome toto
Actual Result:
ClassCastException
ERROR MESSAGES/STACK TRACES THAT OCCUR :
root cause
org.apache.jasper.JasperException: Unable to convert string 'toto' to
class
java.lang.String for attribute username: java.lang.ClassCastException
at org.apache.jasper.runtime.JspRuntimeLibrary.convert
(JspRuntimeLibrary.java:184)
at
org.apache.jasper.runtime.JspRuntimeLibrary.internalIntrospecthelper
(JspRuntimeLibrary.java:267)
at org.apache.jasper.runtime.JspRuntimeLibrary.introspecthelper
(JspRuntimeLibrary.java:219)
at org.apache.jsp.welcome$jsp._jspService(welcome$jsp.java:105)
REPRODUCIBILITY :
This bug can be reproduced always.
-- BEGIN SOURCE --
File LoginBean.java
===
public class LoginBean {
private String username = ;
public void setUsername(String username) {this.username = username;}
public String getUsername() {return username;}
}
File LoginBeanBeanInfo.java
===
import java.beans.*;
import java.io.*;
public class LoginBeanBeanInfo extends SimpleBeanInfo {
private Class beanClass = LoginBean.class;
public LoginBeanBeanInfo() {
}
public PropertyDescriptor[] getPropertyDescriptors() {
try {
PropertyDescriptor _username = new PropertyDescriptor(username,
beanClass, getUsername, setUsername);
_username.setDisplayName(username);
_username.setShortDescription(username);
_username.setPropertyEditorClass(javax.swing.JTextField.class);
PropertyDescriptor[] pds = new PropertyDescriptor[] {_username};
return pds;
}
catch(IntrospectionException ex) {
ex.printStackTrace();
return null;
}
}
}
File login.jsp
===
html
head
titlelogin/title
/head
jsp:useBean id=loginBeanId scope=session class=LoginBean /
body
h1Login Page/h1
form method=post action=%=
request.getContextPath()+/welcome.jsp%
brUsername : input name=usernamebr
input type=submit name=Submit value=OK
input type=reset value=Reset
/form
/body
/html
File welcome.jsp
===
%@page import=LoginBean%
html
headtitleWelcome Page/title/head
body
jsp:useBean id=loginBeanId scope=session class=LoginBean /
jsp:setProperty name=loginBeanId property=username /
Welcome jsp:getProperty name=loginBeanId property=username /
/body
/html
-- END SOURCE --
CUSTOMER WORKAROUND :
replace the line
jsp:setProperty name=loginBeanId property=username /
by
%
String s = request.getParameter(username);
loginBeanId.setUsername(s);
%
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
extends JSP
Hello, is there any constraints in extending a JSP : i use %@ page extends=myjsp % is there any performance issue ? Thanks -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources ImmutableNameNotFoundException.java ProxyDirContext.java
remm2002/10/14 07:31:23
Modified:catalina/src/share/org/apache/naming/resources
ProxyDirContext.java
Added: catalina/src/share/org/apache/naming/resources
ImmutableNameNotFoundException.java
Log:
- Port patch.
- Save on NamingException object creation.
Revision ChangesPath
1.14 +13 -5
jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ProxyDirContext.java
Index: ProxyDirContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ProxyDirContext.java,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- ProxyDirContext.java 4 Oct 2002 12:26:10 - 1.13
+++ ProxyDirContext.java 14 Oct 2002 14:31:23 - 1.14
@@ -76,6 +76,7 @@
import javax.naming.Name;
import javax.naming.NameParser;
import javax.naming.NamingEnumeration;
+import javax.naming.NameNotFoundException;
import javax.naming.NamingException;
import javax.naming.directory.DirContext;
import javax.naming.directory.Attributes;
@@ -210,6 +211,13 @@
protected int cacheObjectMaxSize = 32768; // 32 KB
+/**
+ * Immutable name not found exception.
+ */
+protected NameNotFoundException notFoundException =
+new ImmutableNameNotFoundException();
+
+
// - Public Methods
@@ -1396,7 +1404,7 @@
}
}
if (!cacheEntry.exists) {
-throw new NamingException(Resource not found);
+throw notFoundException;
}
return (cacheEntry);
}
1.1
jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ImmutableNameNotFoundException.java
Index: ImmutableNameNotFoundException.java
===
/*
* $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/resources/ImmutableNameNotFoundException.java,v
1.1 2002/10/14 14:31:23 remm Exp $
* $Revision: 1.1 $
* $Date: 2002/10/14 14:31: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,
cvs commit: jakarta-tomcat-catalina/catalina/src/conf catalina.conf.xml
remm2002/10/14 07:44:49 Removed: catalina/src/conf catalina.conf.xml Log: - Removed outdated configuration file. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: extends JSP
do you know if there are any constraints except these defined in JSP 8.2.4 Thanks for any help or experience Thomas Colin de Verdière wrote: Hello, is there any constraints in extending a JSP : i use %@ page extends=myjsp % is there any performance issue ? Thanks -- Thomas Colin de Verdière SCORT http://www.scort.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13606] New: - Compiler not thread safe
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=13606. 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=13606 Compiler not thread safe Summary: Compiler not thread safe Product: Tomcat 4 Version: 4.1.12 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Jasper 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have applied the 5.0 patch for this into 4.1.12 and it still does not work. If I have two browsers try and load the same uncompiled jsp at the same time one gets a null pointer exception. I think it might happen before the compile where the second page deletes the .java file at the same time the first page trys to compile it but not sure. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13606] - Compiler not thread safe
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=13606. 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=13606 Compiler not thread safe [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 15:11 --- As with many of your bug reports, there's simply not enough information to be able to reproduce them. You seem to assume that people reading them have access to your computer. I also have no idea what is the 5.0 patch for this. Please be specific. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build2.xml
costin 2002/10/14 10:00:09
Modified:.build2.xml
Log:
Update for the recent changes.
Revision ChangesPath
1.6 +3 -20 jakarta-tomcat-5/build2.xml
Index: build2.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build2.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build2.xml20 Aug 2002 19:02:40 - 1.5
+++ build2.xml14 Oct 2002 17:00:09 - 1.6
@@ -6,6 +6,7 @@
!-- See build.properties.sample in the top level directory for all --
!-- property values you must customize for successful building!!!--
+
property file=${user.home}/build.properties/
property file=build.properties/
property file=build.properties.default/
@@ -47,7 +48,7 @@
pathelement location=${activation.jar}/
pathelement location=${jta.jar}/
-pathelement location=${optit.jar}/
+pathelement location=${jasper.home}/lib/jsp20el.jar/
/path
patternset id=static.res
@@ -98,7 +99,7 @@
path location=${commons.home}/logging/src/java /
path location=${commons.home}/discovery/src/java /
/src
- exclude name=org/apache/tomcat/util/net/PureTLS* /
+ exclude name=org/apache/tomcat/util/net/puretls/PureTLS* /
exclude name=org/apache/commons/logging/impl/LogKitLogger.java /
exclude name=org/apache/commons/modeler/impl/IntrospectionModeler.java /
@@ -282,24 +283,6 @@
/target
target name=discovery
-path id=discoveryCP
- path refid=alljars/
- path refid=jasperjars/
- pathelement location=${build.dir}/classes/
- pathelement location=${ant.home}/lib/xercesImpl.jar/
- pathelement location=${ant.home}/lib/xml-apis.jar/
- pathelement location=${ant.home}/lib/ant.jar/
- pathelement location=${tools.jar}/
- pathelement location=/usr/share/java/xalan-j_2_3_1/bin/xercesImpl.jar/
- /path
-
-taskdef name=discovery
- classname=org.apache.commons.discovery.ServiceDiscoveryTask
- classpathref=discoveryCP/
-
-discovery debug=1 id=myDiscovery
- serviceName=javax.xml.parsers.SAXParserFactory /
-echo message=Found ${jxpath:/references[@name='myDiscovery']} /
/target
target name=jdepend description=Document the dependency graph
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[5.0] building ?
Just a small question ( Remy ? ) - what targets do you actually use when building ? For me it takes forever if I do a build in tomcat5 - it goes and tries to generate javadoc and examples for servlet, it does dozens of calls and 'deployements'. Is there any magic trick to actually recompile only a part of tomcat ? -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5/resources catalina-main.manifest
costin 2002/10/14 10:01:29 Added: resources catalina-main.manifest Log: A small ( experimental ) manifest for the (almost :-) single-jar tomcat5. Revision ChangesPath 1.1 jakarta-tomcat-5/resources/catalina-main.manifest Index: catalina-main.manifest === Main-Class: org.apache.catalina.startup.Catalina Class-Path: classes/ ../classes/ log4j.jar -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [5.0] building ?
Costin Manolache wrote: Just a small question ( Remy ? ) - what targets do you actually use when building ? When building to test/develop, the default target. I use release to build a binary. For me it takes forever if I do a build in tomcat5 - it goes and tries to generate javadoc and examples for servlet, it does dozens of calls and 'deployements'. Is there any magic trick to actually recompile only a part of tomcat ? No, but: - my computer is relatively fast (P4m 1.6 these days) - I'll get a new one a lot faster really soon :) But maybe we could work on your updated script (you said it was a lot faster), and add the utility targets to it. quote A small ( experimental ) manifest for the (almost :-) single-jar tomcat5. /quote Hey, that was my idea (I also wanted to be able to configure the classloaders) ;-) You did it already ? Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [5.0] building ?
Remy Maucherat wrote: No, but: - my computer is relatively fast (P4m 1.6 these days) - I'll get a new one a lot faster really soon :) Well, I prefer laptops - and I prefer light over fast. And those things are quite expensive. But maybe we could work on your updated script (you said it was a lot faster), and add the utility targets to it. It is faster, but it's only good to compile stuff ( well, it can also start tomcat, but that's still too experimental ). BTW, related - are the tests working ? What's the right script and order to run jsp and container tests ? I would like a target to run the tests ( and to get that into gump ). quote A small ( experimental ) manifest for the (almost :-) single-jar tomcat5. /quote Hey, that was my idea (I also wanted to be able to configure the classloaders) ;-) You did it already ? No, I just worked around :-) That's the equivalent of a 'standalone' tomcat33, i.e. everything is in a single .jar, no classpath hierarchy or anything else. Just add water ( I mean a webapps/ and conf/ dir ) and run. Not completely working, but it's close. -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[VOTE] tomcat-commiters list
I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [ ] I agree with the proposal [ ] I don't agree with the proposal -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Configuring TOMCAT 3.3 with IIS 4.0
Hi, I am having problems trying to configure TOMCAT 3.3 to work with IIS 4.0, via isapi_redirect.dll When I am doing an upload of a file larger than 100Mbytes I get an 'out of memory' error. I already tried to set the parameters cmd_line= -Xmx256m -Xss64k to the file wrapper.properties. If I ran TOMCAT stand alone (without IIS integration) it works fine, but when it is under IIS I receive the 'out of memory' error. The server is a NT-40 - Service Pack 6, with 198 Mbytes Ram memory and 300 Mbytes of Virtual Memory. It seems that when it is under IIS it is ignoring the memory parameters -Xmx256m -Xss64k. Is there any other configuration that I am missing ? thanks Moisés Bezerra de Menezes Camminus Consultores tel.55 11 9658-4212 [EMAIL PROTECTED] [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13606] - Compiler not thread safe
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=13606.
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=13606
Compiler not thread safe
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2002-10-14 17:51 ---
Ok.. I will be as descriptive as I can.
I have a jsp page lets call it a.jsp
I have two browser windows try and access a.jsp at the same time. If a.jsp has
changed since last compile time or a.jsp has not been compiled then one browser
window will get a NPE and the other will load the jsp page fine. This shows up
more on a dual processor system then on a single. I have added the code from
tomcat 5 o.a.j.c.Compiler to 4.1.12 that syncronizes the javac.execute() call
try {
synchronized(javacLock) {
javac.execute();
}
} catch (BuildException e) {
success = false;
}
I believe what is happening is the first call to a.jsp starts to create
the .java file, the second call then sees this .java file and attempts to
compile it before the .java file is finished being generated or something like
that. I have been unable to create a test outside of our application that has
this behavior on a regular basis, but our application can reproduce it
consistantly as its pages take a lot longer to compile.
here is the stacktrace that it creates
2002-10-14 10:55:34 ApplicationDispatcher[] Servlet.service() for servlet jsp
threw exception
org.apache.jasper.JasperException
at org.apache.jasper.servlet.JspServletWrapper.service
(JspServletWrapper.java:248)
at org.apache.jasper.servlet.JspServlet.serviceJspFile
(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationDispatcher.invoke
(ApplicationDispatcher.java:684)
at org.apache.catalina.core.ApplicationDispatcher.doForward
(ApplicationDispatcher.java:432)
at org.apache.catalina.core.ApplicationDispatcher.forward
(ApplicationDispatcher.java:356)
at com.controlj.green.web.servlets.NavigationMapperServlet.doGet
(NavigationMapperServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke
(AuthenticatorBase.java:471)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNex
t(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:174)
at
Re: [VOTE] tomcat-commiters list
Costin Manolache wrote: I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [X] I agree with the proposal [ ] I don't agree with the proposal Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13556] - release builds bad tar file
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=13556. 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=13556 release builds bad tar file [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 18:29 --- Isn't this a documentation bug then? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] tomcat-commiters list
Though I'm not a committer and thus can't vote I think a legitimate concern created by a list like this would be that the real bulk of threads that should occur on the tomcat developer list might migrate into this closed list and away from the more public view. Just a thought to consider. Jason -Original Message- I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [ ] I agree with the proposal [ ] I don't agree with the proposal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13556] - release builds bad tar file
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=13556. 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=13556 release builds bad tar file [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 18:36 --- No, it's in big, bold letters on the download page. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
The proposal needs to identify a moderator. The moderator will be the one who approves subscription requests (as well as filtering out spam). - Sam Ruby -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
- Original Message - From: Costin Manolache [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 14, 2002 10:24 AM Subject: [VOTE] tomcat-commiters list I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [ ] I agree with the proposal [X] I don't agree with the proposal Security holes don't occur often enough to bother with maintaining the active committers list, and there isn't much point in the list otherwise. Plus, segregating the security concerns simply would make the mbox archives a must-bookmark for every black-hat. :) -- 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: [VOTE] tomcat-commiters list
Sam Ruby wrote: The proposal needs to identify a moderator. The moderator will be the one who approves subscription requests (as well as filtering out spam). I can do that. ( unless someone else wants to ). -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
Bill Barker wrote: I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [ ] I agree with the proposal [X] I don't agree with the proposal Security holes don't occur often enough to bother with maintaining the active committers list, and there isn't much point in the list otherwise. Plus, segregating the security concerns simply would make the mbox archives a must-bookmark for every black-hat. :) Aparently they do occur more often than we would like. And I've been in at least 4 Cc: chains in the last 2 months. Whoever is in the the apache security list or PMC should forward tomcat security problems to a known address where it can be addressed. It is not only for security - but any issue that we might consider 'private' ( again, it is better than using the Cc: ). -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [5.0] building ?
On Monday 14 October 2002 01:19 pm, Costin Manolache wrote: Remy Maucherat wrote: No, but: - my computer is relatively fast (P4m 1.6 these days) - I'll get a new one a lot faster really soon :) Well, I prefer laptops - and I prefer light over fast. And those things are quite expensive. But maybe we could work on your updated script (you said it was a lot faster), and add the utility targets to it. It is faster, but it's only good to compile stuff ( well, it can also start tomcat, but that's still too experimental ). BTW, related - are the tests working ? What's the right script and order to run jsp and container tests ? I would like a target to run the tests ( and to get that into gump ). watchdog works, and the small number of unit tests targeted by the test target works. Catalina's tester doesn't work. I've posted patches to make it work. I can repost, if it would be useful. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13583] - Relative includes/forwards with ../s broken
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=13583. 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=13583 Relative includes/forwards with ../s broken --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 20:01 --- Created an attachment (id=3461) A zip including a war and the source for the war -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13583] - Relative includes/forwards with ../s broken
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=13583. 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=13583 Relative includes/forwards with ../s broken --- Additional Comments From [EMAIL PROTECTED] 2002-10-14 20:03 --- Sorry I didn't make this clearer! I have now verified that it only happens when the webapp is served from a war (as when deployed on JBoss/Tomcat or on Tomcat with unpackWARS=false). The attachment above is a WAR that is probably very similar to the test code you have used, I have verified that the bug exists on Tomcat 4.1.12 and Tomcat 4.1.10. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
There's currently a call for project committers to be on the [EMAIL PROTECTED] list. This list intends to be the clearinghouse for all ASF project related security issues, not just httpd. Costin, Craig, et al.: the deal seems to be that each major project version have someone who's a committer subscribed as a project liason. So it might make sense if you both signed up, or if other committers wanted to step forward...I would leave that to you all to figure out. Not to short-circuit a Tomcat committers list, because there may well be issues other than security to deal with, and it would make sense to have information flow between security@ and a proposed tomcat-committers@ anyway (I'm thinking the detailed hashing of fixes would happen on the latter list). Just my $0.02. Chuck On Monday, October 14, 2002, at 12:14 PM, Costin Manolache wrote: Bill Barker wrote: I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [ ] I agree with the proposal [X] I don't agree with the proposal Security holes don't occur often enough to bother with maintaining the active committers list, and there isn't much point in the list otherwise. Plus, segregating the security concerns simply would make the mbox archives a must-bookmark for every black-hat. :) Aparently they do occur more often than we would like. And I've been in at least 4 Cc: chains in the last 2 months. Whoever is in the the apache security list or PMC should forward tomcat security problems to a known address where it can be addressed. It is not only for security - but any issue that we might consider 'private' ( again, it is better than using the Cc: ). -- Costin -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
On 14/10/02 19:45, Sam Ruby [EMAIL PROTECTED] wrote: The proposal needs to identify a moderator. The moderator will be the one who approves subscription requests (as well as filtering out spam). And AFAIK, we've roughly always said no to extra mailing list (but -dev -cvs and -users) to keep all projects more-or-less in sync... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
Chuck Murcko wrote: There's currently a call for project committers to be on the [EMAIL PROTECTED] list. This list intends to be the clearinghouse for all ASF project related security issues, not just httpd. Costin, Craig, et al.: the deal seems to be that each major project version have someone who's a committer subscribed as a project liason. So it might make sense if you both signed up, or if other committers wanted to step forward...I would leave that to you all to figure out. Not to short-circuit a Tomcat committers list, because there may well be issues other than security to deal with, and it would make sense to have information flow between security@ and a proposed tomcat-committers@ anyway (I'm thinking the detailed hashing of fixes would happen on the latter list). Regarding [EMAIL PROTECTED] - I think that all who play the role of release manager should be on the list ( i.e. Remy, Larry, Mladen, Henri). It seems to be open for a limited number of 'liasons' ( I hope it is more than one, as we have several major components ). My preference is that any tomcat commiter who is interested to be able to get this info and discuss ( and hopefully fix ) tomcat security issues. I hope that whoever gets the security messages will fix them or forward them to tomcat-commiters - but that's of course his choice. If the apache list is open to any commiter - I'll certainly subscribe ( and I hope most active tomcat commiters will do the same ! ), but that doesn't remove the need for a private list for tomcat commiters. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13616] New: - Encoding in JSP Document(JSP in XML Syntax) is not translated properly.
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=13616. 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=13616 Encoding in JSP Document(JSP in XML Syntax) is not translated properly. Summary: Encoding in JSP Document(JSP in XML Syntax) is not translated properly. Product: Tomcat 4 Version: 4.1.12 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] simple example: jsp:root xmlns:jsp=http://java.sun.com/JSP/Page; version=1.2 jsp:directive.page contentType=text/html; charset=Big5 pageEncoding=Big5 language=java/ jsp:text![CDATA[ html head titlePage Encoding Test/title /head body !-- Bib5 encoding -- p#20986;#29256;#26989;#21209;/p !-- Bib5 encoding -- /body /html ]]/jsp:text /jsp:root -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] tomcat-commiters list
Jason Corley wrote: Though I'm not a committer and thus can't vote I think a legitimate concern created by a list like this would be that the real bulk of threads that should occur on the tomcat developer list might migrate into this closed list and away from the more public view. Just a thought to consider. Sorry I didn't made this more clear. The tomcat-dev mailing list is and remains the place where all development issues are discussed. I think there are plenty of tomcat commiters who wouldn't allow such thing to happen. -- Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
PATCH: compile-only for servletapi
This will avoid the full javadoc/examples/etc when building tomcat5,
and will also avoid some copy.
Costin
Index: jsr152/build.xml
===
RCS file: /home/cvs/jakarta-servletapi-5/jsr152/build.xml,v
retrieving revision 1.3
diff -u -r1.3 build.xml
--- jsr152/build.xml9 Sep 2002 18:01:20 - 1.3
+++ jsr152/build.xml14 Oct 2002 20:28:23 -
@@ -15,6 +15,7 @@
property name=jsp-api.buildvalue=build/
property name=jsp-api.dist value=dist/
property name=servlet-api.jar
value=../jsr154/dist/lib/servlet-api.jar/
+ property name=jsp-api.jar value=${jsp-api.dist}/lib/jsp-api.jar/
path id=examples.classpath
pathelement location=${jsp-api.build}/classes/
@@ -137,13 +138,8 @@
!-- = Distribution Files =
--
- target name=dist depends=compile,examples,javadoc
- description=Create binary distribution
-
-!-- Copy Javadocs --
-copy todir=${jsp-api.dist}/docs/api
-fileset dir=${jsp-api.build}/docs/api/
-/copy
+ target name=jar depends=compile
+ description=Create jar
!-- Prepare Manifest --
copy tofile=${jsp-api.build}/manifest
@@ -155,9 +151,21 @@
/copy
!-- Create JAR file --
-jar jarfile=${jsp-api.dist}/lib/jsp-api.jar
+jar jarfile=${jsp-api.jar}
basedir=${jsp-api.build}/classes
- manifest=${jsp-api.build}/manifest/
+ manifest=${jsp-api.build}/manifest
+ include name=javax/servlet/jsp/** /
+/jar
+
+ /target
+
+ target name=dist depends=compile,examples,javadoc,jar
+ description=Create binary distribution
+
+!-- Copy Javadocs --
+copy todir=${jsp-api.dist}/docs/api
+fileset dir=${jsp-api.build}/docs/api/
+/copy
!-- Copy API source files --
copy todir=${jsp-api.dist}/src
Index: jsr154/build.xml
===
RCS file: /home/cvs/jakarta-servletapi-5/jsr154/build.xml,v
retrieving revision 1.2
diff -u -r1.2 build.xml
--- jsr154/build.xml27 Aug 2002 13:20:35 - 1.2
+++ jsr154/build.xml14 Oct 2002 20:28:23 -
@@ -14,7 +14,7 @@
property name=implementation.revision value=public_draft/
property name=servlet-api.buildvalue=build/
property name=servlet-api.dist value=dist/
-
+ property name=servlet-api.jar
value=${servlet-api.dist}/lib/servlet-api.jar/
path id=examples.classpath
pathelement location=${servlet-api.build}/classes/
/path
@@ -122,13 +122,8 @@
!-- = Distribution Files =
--
- target name=dist depends=compile,examples,javadoc
- description=Create binary distribution
-
-!-- Copy Javadocs --
-copy todir=${servlet-api.dist}/docs/api
-fileset dir=${servlet-api.build}/docs/api/
-/copy
+ target name=jar depends=compile
+ description=Create the jar
!-- Prepare Manifest --
copy tofile=${servlet-api.build}/manifest
@@ -140,9 +135,22 @@
/copy
!-- Create JAR file --
-jar jarfile=${servlet-api.dist}/lib/servlet-api.jar
+jar jarfile=${servlet-api.jar}
basedir=${servlet-api.build}/classes
- manifest=${servlet-api.build}/manifest/
+ manifest=${servlet-api.build}/manifest
+ include name=javax/servlet/**/
+ exclude name=javax/servlet/jsp/**/
+/jar
+
+ /target
+
+ target name=dist depends=compile,examples,javadoc,jar
+ description=Create binary distribution
+
+!-- Copy Javadocs --
+copy todir=${servlet-api.dist}/docs/api
+fileset dir=${servlet-api.build}/docs/api/
+/copy
!-- Copy API source files --
copy todir=${servlet-api.dist}/src
--
Costin
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] catalina.sh and cygwin
Hi, I proposed this patch before without any notice. No problem at all, you all seem very busy. But I got several people asking for help regarding this issue, so I resend the patch. The problem is, that catalina.sh does not translate the $CATALINA_TMPDIR path to cygwin-path resulting tomcat in throwing these nasty ContextConfig[] Exception processing JAR at resource path - Exceptions. Here's a patch for that (against the 4.1.12 RELEASE) --- catalina_orig.sh2002-09-23 11:23:00.0 +0200 +++ catalina.sh 2002-09-27 20:38:36.0 +0200 @@ -101,6 +101,7 @@ CATALINA_HOME=`cygpath --path --windows $CATALINA_HOME` CATALINA_BASE=`cygpath --path --windows $CATALINA_BASE` CLASSPATH=`cygpath --path --windows $CLASSPATH` + CATALINA_TMPDIR=`cygpath --path --windows $CATALINA_TMPDIR` JSSE_HOME=`cygpath --path --windows $JSSE_HOME` fi I hope I did it the right way. Peter -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina build.xml
costin 2002/10/14 14:21:32
Modified:catalina build.xml
Log:
A small change to allow 'light' builds. The normal build should
be identical ( since the old target is called ), I just added
made compile/jar separate.
Revision ChangesPath
1.24 +6 -2 jakarta-tomcat-catalina/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/build.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- build.xml 11 Oct 2002 10:55:07 - 1.23
+++ build.xml 14 Oct 2002 21:21:32 - 1.24
@@ -837,8 +837,8 @@
!-- == DEPLOY: Create Catalina JARs --
- target name=deploy-catalina depends=deploy-static,build-main
- description=Build and deploy Catalina component
+ target name=catalina-jars depends=deploy-static,build-catalina
+ description=Build catalina jars
!-- Catalina Bootstrap JAR File --
jar jarfile=${catalina.deploy}/bin/bootstrap.jar
@@ -961,6 +961,10 @@
/fileset
/jar
+ /target
+
+ target name=deploy-catalina depends=deploy-static,build-main,catalina-jars
+ description=Build and deploy Catalina component
/target
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
On Monday, October 14, 2002, at 01:40 PM, Costin Manolache wrote: Chuck Murcko wrote: There's currently a call for project committers to be on the [EMAIL PROTECTED] list. This list intends to be the clearinghouse for all ASF project related security issues, not just httpd. Costin, Craig, et al.: the deal seems to be that each major project version have someone who's a committer subscribed as a project liason. So it might make sense if you both signed up, or if other committers wanted to step forward...I would leave that to you all to figure out. Not to short-circuit a Tomcat committers list, because there may well be issues other than security to deal with, and it would make sense to have information flow between security@ and a proposed tomcat-committers@ anyway (I'm thinking the detailed hashing of fixes would happen on the latter list). Regarding [EMAIL PROTECTED] - I think that all who play the role of release manager should be on the list ( i.e. Remy, Larry, Mladen, Henri). It seems to be open for a limited number of 'liasons' ( I hope it is more than one, as we have several major components ). My preference is that any tomcat commiter who is interested to be able to get this info and discuss ( and hopefully fix ) tomcat security issues. I hope that whoever gets the security messages will fix them or forward them to tomcat-commiters - but that's of course his choice. If the apache list is open to any commiter - I'll certainly subscribe ( and I hope most active tomcat commiters will do the same ! ), but that doesn't remove the need for a private list for tomcat commiters. Yes, the security list is open to all committers, and it is not a 1:1 mapping of projects to committers/subscribers. Definitely all the RMs should be on it, as well as interested committers from each project/major component. I should have said at least one somewhere before, especially if a fix needs to get rolled out quickly and precisely. As for other issues needing a private and local (to Tomcat) list, I must leave that to you all to decide. After thinking about it a bit more MHO is that a separate committers list really sounds equivalent to having committer participation on the PMC list for jakarta, if that is possible. Chuck -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
MBeanException w/AJP13Connector and (hopefully) its solution
When I uncomment the AJP13 Connector, I get the following exception on startup: ServerLifecycleListener: createMBeans: MBeanException java.lang.Exception: ManagedBean is not found with Ajp13Connector at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:225) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:369) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:777) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:751) at org.apache.catalina.mbeans.ServerLifecycleListener.createMBeans(ServerLifecycleListener.java:339) at org.apache.catalina.mbeans.ServerLifecycleListener.lifecycleEvent(ServerLifecycleListener.java:206) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2182) at org.apache.catalina.startup.Catalina.start(Catalina.java:510) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) I'm wondering if the fix is simply to add a section into catalina/src/share/o/a/c/mbeans/mbeans-descriptors.xml, describing the AJP 13 connector? I've attached my naive fix to this, which is to copy the Coyote connector section, removing only the protocolHandler attribute, since that is unique to Coyote(if I'm not mistaken, I very well could be). Could I get one of the committers to review this please and submit the change? We need this for NetWare, which does not have a port of mod_jk2 yet. Thanks, Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., the leading provider of Net business solutions http://www.novell.com mbeans-descriptors.patch Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-servletapi-5/jsr154 build.xml
kinman 2002/10/14 15:44:07
Modified:jsr152 build.xml
jsr154 build.xml
Log:
- Patch by Costin
This will avoid the full javadoc/examples/etc when building tomcat5,
and will also avoid some copy.
Revision ChangesPath
1.4 +17 -9 jakarta-servletapi-5/jsr152/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-servletapi-5/jsr152/build.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build.xml 9 Sep 2002 18:01:20 - 1.3
+++ build.xml 14 Oct 2002 22:44:07 - 1.4
@@ -15,6 +15,7 @@
property name=jsp-api.buildvalue=build/
property name=jsp-api.dist value=dist/
property name=servlet-api.jar value=../jsr154/dist/lib/servlet-api.jar/
+ property name=jsp-api.jar value=${jsp-api.dist}/lib/jsp-api.jar/
path id=examples.classpath
pathelement location=${jsp-api.build}/classes/
@@ -137,13 +138,8 @@
!-- = Distribution Files = --
- target name=dist depends=compile,examples,javadoc
- description=Create binary distribution
-
-!-- Copy Javadocs --
-copy todir=${jsp-api.dist}/docs/api
-fileset dir=${jsp-api.build}/docs/api/
-/copy
+ target name=jar depends=compile
+ description=Create jar
!-- Prepare Manifest --
copy tofile=${jsp-api.build}/manifest
@@ -155,9 +151,21 @@
/copy
!-- Create JAR file --
-jar jarfile=${jsp-api.dist}/lib/jsp-api.jar
+jar jarfile=${jsp-api.jar}
basedir=${jsp-api.build}/classes
- manifest=${jsp-api.build}/manifest/
+ manifest=${jsp-api.build}/manifest
+ include name=javax/servlet/jsp/** /
+/jar
+
+ /target
+
+ target name=dist depends=compile,examples,javadoc,jar
+ description=Create binary distribution
+
+!-- Copy Javadocs --
+copy todir=${jsp-api.dist}/docs/api
+fileset dir=${jsp-api.build}/docs/api/
+/copy
!-- Copy API source files --
copy todir=${jsp-api.dist}/src
1.3 +18 -10jakarta-servletapi-5/jsr154/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-servletapi-5/jsr154/build.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- build.xml 27 Aug 2002 13:20:35 - 1.2
+++ build.xml 14 Oct 2002 22:44:07 - 1.3
@@ -14,7 +14,7 @@
property name=implementation.revision value=public_draft/
property name=servlet-api.buildvalue=build/
property name=servlet-api.dist value=dist/
-
+ property name=servlet-api.jar value=${servlet-api.dist}/lib/servlet-api.jar/
path id=examples.classpath
pathelement location=${servlet-api.build}/classes/
/path
@@ -122,13 +122,8 @@
!-- = Distribution Files = --
- target name=dist depends=compile,examples,javadoc
- description=Create binary distribution
-
-!-- Copy Javadocs --
-copy todir=${servlet-api.dist}/docs/api
-fileset dir=${servlet-api.build}/docs/api/
-/copy
+ target name=jar depends=compile
+ description=Create the jar
!-- Prepare Manifest --
copy tofile=${servlet-api.build}/manifest
@@ -140,9 +135,22 @@
/copy
!-- Create JAR file --
-jar jarfile=${servlet-api.dist}/lib/servlet-api.jar
+jar jarfile=${servlet-api.jar}
basedir=${servlet-api.build}/classes
- manifest=${servlet-api.build}/manifest/
+ manifest=${servlet-api.build}/manifest
+ include name=javax/servlet/**/
+ exclude name=javax/servlet/jsp/**/
+/jar
+
+ /target
+
+ target name=dist depends=compile,examples,javadoc,jar
+ description=Create binary distribution
+
+!-- Copy Javadocs --
+copy todir=${servlet-api.dist}/docs/api
+fileset dir=${servlet-api.build}/docs/api/
+/copy
!-- Copy API source files --
copy todir=${servlet-api.dist}/src
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13619] New: - TagInfo.getAttributes returns a zero-length array instead of null if a tag has not defined attributes.
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=13619. 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=13619 TagInfo.getAttributes returns a zero-length array instead of null if a tag has not defined attributes. Summary: TagInfo.getAttributes returns a zero-length array instead of null if a tag has not defined attributes. Product: Tomcat 5 Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Jasper2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] According to the javadocs, TagInfo.getAttributes must return null if the tag in question is defined with no attributes. Looking at line 280 of o.a.j.c.TagFileProcessor.java, the size of a vector is used to initialize the size of the array, so if the even if the vector has no elements the array is initialized and passed to the constructor of TagInfo. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 build.xml
costin 2002/10/14 16:09:44
Modified:.build.xml
Log:
Added a target that will only build, with minimal copy. It can be
used for develoment ( when you modify a file and want a quick build
to see the result ).
If you have a super-fast computer, just use the normal target :-)
Also added a target to update all source repositories that we
use.
Note that the target won't work unless the servlet patch is
applied ( that shouldn't affect existing targets ).
Revision ChangesPath
1.44 +129 -3jakarta-tomcat-5/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- build.xml 14 Oct 2002 09:25:08 - 1.43
+++ build.xml 14 Oct 2002 23:09:44 - 1.44
@@ -48,6 +48,10 @@
property name=webapps.buildvalue=${catalina.home}/webapps/build/
property name=webapps.dist value=${catalina.home}/webapps/dist/
+ !-- Some compilers will disable debugging if true. And it doesn't do anything
+ in most cases --
+ property name=compile.optimize value=false/
+
!-- === DETECT: Display configuration == --
target name=detect
@@ -65,18 +69,113 @@
!-- = DEPLOY: Create Directories === --
- target name=deploy-prepare
+ target name=init
mkdir dir=${tomcat.build}/
+mkdir dir=${tomcat.build}/classes /
+
+uptodate property=servletapi.build.notrequired
+ targetfile=${tomcat.build}/common/lib/servlet-api.jar
+ srcfiles dir=${api.home}/jsr154/src includes=** /
+/uptodate
+uptodate property=jspapi.build.notrequired
+ targetfile=${tomcat.build}/common/lib/jsp-api.jar
+ srcfiles dir=${api.home}/jsr152/src includes=** /
+/uptodate
+
+uptodate property=tomcatutil.build.notrequired
+ targetfile=${tomcat.build}/server/lib/tomcat-util.jar
+ srcfiles dir=${jtc.home}/util/java includes=** /
+/uptodate
+
/target
!-- == DEPLOY: Copy Static Files === --
- target name=deploy-static depends=deploy-prepare/
+ target name=deploy-static depends=init/
+
+
+ !-- == Build all components === --
+ target name=build-servletapi unless=servletapi.build.notrequired
+echo== Building: ${servlet-api.jar}/echo
+
+ant dir=${api.home}/jsr154 target=jar
+property name=servlet-api.build value=${tomcat.build} /
+property name=servlet-api.jar
value=${tomcat.build}/common/lib/servlet-api.jar/
+/ant
+ /target
+
+ target name=build-jspapi unless=jspapi.build.notrequired
+echo== Building: ${jsp-api.jar}/echo
+ant dir=${api.home}/jsr152 target=jar
+property name=jsp-api.build value=${tomcat.build} /
+property name=jsp-api.jar
value=${tomcat.build}/common/lib/jsp-api.jar/
+/ant
+ /target
+
+ target name=build-tomcatutil unless=tomcatutil.build.notrequired
+echo== Building: tomcat-util /echo
+
+ant dir=${jtc.home}/util target=build-main
+ property name=jmx.jar value=${jmx.jar} /
+ property name=puretls.jar value=${puretls.jar} /
+ property name=jsse.lib value=${jsse.lib} /
+
+ property name=tomcat-util.build value=${tomcat.build} /
+ property name=tomcat-util.lib value=${tomcat.build}/server/lib /
+/ant
+ /target
+
+ target name=build depends=init,build-servletapi,build-jspapi,build-tomcatutil
+ description=Builds all components
+
+echo== Building: catalina /echo
+
+ant dir=${catalina.home}/catalina target=catalina-jars
+!-- in-place building --
+property name=catalina.build value=${tomcat.build} /
+property name=catalina.deploy value=${tomcat.build} /
+property name=flags.hide value=true /
+/ant
+
+echo== Building: tomcat-coyote /echo
+
+ant dir=${jtc.home}/coyote target=compile.tomcat5
+ property name=catalina.home value=${tomcat.build}/
+ property name=tomcat5.detect value=true/
+ property name=servlet.jar value=${servlet-api.jar}/
+/ant
+echo== Building: tomcat-jk /echo
+
+ant dir=${jtc.home}/jk target=build-main
+ property name=tomcat41.home value=${tomcat.build}/
+ property name=catalina.home value=${tomcat.build}/
+ property name=commons-logging.jar value=${commons-logging.jar}/
+ property name=jmx.jar value=${jmx.jar}/
+/ant
+
+echo== Building: tomcat-httpd /echo
+
+ant dir=${jtc.home}/http11 target=compile
+ property name=commons-logging.jar
Re: [VOTE] tomcat-commiters list
On Tue, 2002-10-15 at 03:24, Costin Manolache wrote: I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [X] I agree with the proposal [ ] I don't agree with the proposal -- Costin -- 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 TagFileProcessor.java
kinman 2002/10/14 16:18:58
Modified:jasper2/src/share/org/apache/jasper/compiler
TagFileProcessor.java
Log:
- Fix 13619: TagInfo.getAttributes should return null if there is no attributes.
Revision ChangesPath
1.30 +13 -9
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/TagFileProcessor.java
Index: TagFileProcessor.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/TagFileProcessor.java,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- TagFileProcessor.java 9 Oct 2002 17:41:13 - 1.29
+++ TagFileProcessor.java 14 Oct 2002 23:18:57 - 1.30
@@ -272,13 +272,17 @@
tagclass = Constants.TAG_FILE_PACKAGE_NAME + . + name;
-TagVariableInfo[] tagVariableInfos
-= new TagVariableInfo[variableVector.size()];
-variableVector.copyInto(tagVariableInfos);
+TagVariableInfo[] tagVariableInfos = null;
+if (variableVector.size() 0) {
+tagVariableInfos = new TagVariableInfo[variableVector.size()];
+variableVector.copyInto(tagVariableInfos);
+}
-TagAttributeInfo[] tagAttributeInfo
-= new TagAttributeInfo[attributeVector.size()];
-attributeVector.copyInto(tagAttributeInfo);
+TagAttributeInfo[] tagAttributeInfo = null;
+if (attributeVector.size() 0) {
+tagAttributeInfo = new TagAttributeInfo[attributeVector.size()];
+attributeVector.copyInto(tagAttributeInfo);
+}
return new TagInfo(name,
tagclass,
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13619] - TagInfo.getAttributes returns a zero-length array instead of null if a tag has not defined attributes.
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=13619. 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=13619 TagInfo.getAttributes returns a zero-length array instead of null if a tag has not defined attributes. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] tomcat-commiters list
Costin Manolache wrote: I would like to propose a new mailing list. The list will be closed to commiters only. The main purpose will be discussions of security and other special issues. This should avoid [Cc] threads. The main target should be active commiters - so it should start empty. This is a majority vote. [X] I agree with the proposal [ ] I don't agree with the proposal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13627] New: - can't refresh with thee new jsp file
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=13627. 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=13627 can't refresh with thee new jsp file Summary: can't refresh with thee new jsp file Product: Tomcat 4 Version: 4.1.10 Platform: Other OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Connector:Webapp AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] when I change the jsp file to a new one. the browser also render the old one, even when I restart the PC. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13441] - WebApp Connector not writing status code properly on HTTP/1.1 responses
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=13441. 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=13441 WebApp Connector not writing status code properly on HTTP/1.1 responses [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-15 04:56 --- It appears that this bug report may have been premature. I went back to the connector source tree to double check my compilation and it looks like I may not have compiled the module correctly. I reconfigured and recompiled the module against the binary distribution of Apache 2.0.40 and everything seems to be working now. I hope I didn't waste anyone's time. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 13627] - can't refresh with thee new jsp file
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=13627. 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=13627 can't refresh with thee new jsp file [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-10-15 05:55 --- The functionality appears to be working. Please give detailed information if you'd like to reopen it. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
