DO NOT REPLY [Bug 20851] - POST is not defined in RFC 2068 and is not supported by the Servlet API
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=20851. 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=20851 POST is not defined in RFC 2068 and is not supported by the Servlet API [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 07:40 --- *** This bug has been marked as a duplicate of 20850 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20850] - POST is not defined in RFC 2068 and is not supported by the Servlet API
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=20850. 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=20850 POST is not defined in RFC 2068 and is not supported by the Servlet API --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 07:40 --- *** Bug 20851 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20850] - POST is not defined in RFC 2068 and is not supported by the Servlet API
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=20850. 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=20850 POST is not defined in RFC 2068 and is not supported by the Servlet API [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Component|Unknown |Connector:Coyote HTTP/1.1 Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 07:44 --- As I said, unless you are very careful about closing the connection after each request, you could end up with part of a previous request (here, some binary data) being interpreted as part of the next request HTTP header. So it becomes quite random. I think Coyote is quite conservative in the request delimitation handling, but there are situations where it can't be made to work consistently when dealing with a slightly broken client. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19607] - ant undeploy only stops the Context, but doesn't remove physial files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19607. 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=19607 ant undeploy only stops the Context, but doesn't remove physial files [EMAIL PROTECTED] changed: What|Removed |Added Severity|Major |Normal Version|5.0.1 |5.0.3 --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 08:45 --- This is almost fixed in 5.0.3: expanded folders and the WAR will be removed. The XML will not be removed yet (AFAIK); this will be fixed in 5.0.4. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Module Edit at modules.apache.org
This email was generated through the modules.apache.org site. You can modify your module by going to http://modules.apache.org/edit using ID# 557 as the 'User Name' with the password 'aqabrq6a' (without the single quotes). Once you are logged in you can reset this password. Please reply to this email with any questions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Suggestion: Many virtual hosts in Tomcat - hosts-directory
Hello List, Tomcat has a very nice feature, which allows dropping .xml in the wepapp-directory and automatic deployment of contexts defined therein. I would suggest the same approach for Host definitions. For a lot of installations it would _completely_ eliminate the need for changes in server.xml. I don't know, if such a mechanism is planned for tc5. In this case: could we consider a backport of this feature? I would volunteer for an extension to 4.1. But I would like to hear the opinion of the developers. Here is the to-do-list: - add a parameter to the engine-Tag: virtualHostDir= (default: hosts for example) - (Alternative: the plugin-way: define a listener, which does this) - deploy all defined hostxxx.xml in the given dir on startup. - optional: add an auto-deploy feature like in webapps I don't know yet, how invasive the change would be. I am very grateful for any hints. I would like to contribute the extension, if it is well-integrated and riskless enough for the stable tree. Otherwise: maybe it works at least for me... Please do not hesitate to give any kind of comments! regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Suggestion: Many virtual hosts in Tomcat - hosts-directory
Reinhard Moosauer wrote: Hello List, Tomcat has a very nice feature, which allows dropping .xml in the wepapp-directory and automatic deployment of contexts defined therein. I would suggest the same approach for Host definitions. For a lot of installations it would _completely_ eliminate the need for changes in server.xml. I don't know, if such a mechanism is planned for tc5. In this case: could we consider a backport of this feature? I would volunteer for an extension to 4.1. But I would like to hear the opinion of the developers. Here is the to-do-list: - add a parameter to the engine-Tag: virtualHostDir= (default: hosts for example) - (Alternative: the plugin-way: define a listener, which does this) - deploy all defined hostxxx.xml in the given dir on startup. - optional: add an auto-deploy feature like in webapps I don't know yet, how invasive the change would be. I am very grateful for any hints. I would like to contribute the extension, if it is well-integrated and riskless enough for the stable tree. Otherwise: maybe it works at least for me... Please do not hesitate to give any kind of comments! I'd considered it a lot lately, but decided against it, as it's not as hassle free as you make it sound: the biggest problem is configuring the DNS, so I don't see what the feature would add. With TC 5, you can dynamically add hosts with: - JMX (using some agent) - the admin webapp, like in TC 4.1.x I think that's good enough, and the extra complexity doesn't seem to add something of real value. I'd vote -0 or -1 on the issue. Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP] Build Failure - jakarta-tomcat-jk
This email is autogenerated from the output from:
http://cvs.apache.org/builds/gump/2003-06-23/jakarta-tomcat-jk.html
Buildfile: build.xml
detect:
[echo] jakarta-tomcat-connectors
prepare:
[mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/conf
[copy] Copying 8 files to
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/conf
[copy] Copying 1 file to
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/lib
Overriding previous definition of reference to xml-apis.classpath
report:
[echo] Tomcat33: ${tomcat33.detect}
/home/rubys/jakarta/jakarta-tomcat/build/tomcat/lib/common/tomcat_core.jar
[echo] Tomcat40: true /home/rubys/jakarta/jakarta-tomcat-4.0/build
[echo] Tomcat41: ${tomcat41.detect} /home/rubys/jakarta/jakarta-tomcat-4.1/build
[echo] Tomcat5: ${tomcat5.detect}
/home/rubys/jakarta/jakarta-tomcat-catalina/build
[echo] Apache13: ${apache13.detect} ${apache13.home}
[echo] Apache2: ${apache2.detect} ${apache2.home}
[echo] iPlanet: ${iplanet.detect} ${iplanet.home}
[echo] IIS: ${iis.detect} ${iis.home}
[echo] AOLserver: ${aolserver.detect} ${aolserver.home}
[echo] jmx: /opt/jmx-1_2-ri/jmx/lib/jmxri.jar ${jmx.detect}
/home/rubys/jakarta/jakarta-commons/modeler/dist/commons-modeler.jar true
jkjava:
[javac] Compiling 43 source files to
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/build/classes
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:61:
package org.apache.catalina does not exist
[javac] import org.apache.catalina.*;
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:64:
package javax.servlet does not exist
[javac] import javax.servlet.*;
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/BaseJkConfig.java:61:
package org.apache.catalina does not exist
[javac] import org.apache.catalina.*;
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/BaseJkConfig.java:125:
cannot resolve symbol
[javac] symbol : class LifecycleListener
[javac] location: class org.apache.ajp.tomcat4.config.BaseJkConfig
[javac] public class BaseJkConfig implements LifecycleListener {
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:333:
cannot resolve symbol
[javac] symbol : class Host
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] protected void generateVhostHead(Host host, PrintWriter mod_jk) {
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:355:
cannot resolve symbol
[javac] symbol : class Host
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] protected void generateVhostTail(Host host, PrintWriter mod_jk) {
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:386:
cannot resolve symbol
[javac] symbol : class Context
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] protected void generateStupidMappings(Context context,
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:425:
cannot resolve symbol
[javac] symbol : class Context
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] protected void generateContextMappings(Context context, PrintWriter
mod_jk )
[javac]^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:497:
cannot resolve symbol
[javac] symbol : class Context
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] private void generateWelcomeFiles(Context context, PrintWriter mod_jk
) {
[javac] ^
[javac]
/home/rubys/jakarta/jakarta-tomcat-connectors/jk/java/org/apache/ajp/tomcat4/config/ApacheConfig.java:512:
cannot resolve symbol
[javac] symbol : class Context
[javac] location: class org.apache.ajp.tomcat4.config.ApacheConfig
[javac] private void generateStaticMappings(Context context, PrintWriter
mod_jk ) {
[javac] ^
[javac]
Re: Module Edit at modules.apache.org
I changed email to tomcat-committers and the password. Email me if you need the pwd. Or you can reset it (and the confirm email hopefully won't be so public) -Tim Apache Module Site wrote: This email was generated through the modules.apache.org site. You can modify your module by going to http://modules.apache.org/edit using ID# 557 as the 'User Name' with the password 'aqabrq6a' (without the single quotes). Once you are logged in you can reset this password. Please reply to this email with any questions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21010] New: - Error creating new context
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=21010. 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=21010 Error creating new context Summary: Error creating new context Product: Tomcat 5 Version: 5.0.3 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: Webapps:Administration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Error saving (Commit changes) new context with '/' char into his name, for example i need to create /app/bpb context. Workaround: I create /appbpb context and then I modify the path attribute from /appbpb to /app/bpb into the HOME/conf/Catalina/localhost/appbpb.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21010] - Error creating new context
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=21010. 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=21010 Error creating new context --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 13:33 --- Well, that's a known issue. None of the chars which aren't allowed in a filename are filtered out at the moment, so ... I think this is the same behavior as with TC 4.1.x. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-5 RELEASE-PLAN-5.0.txt
remm2003/06/23 06:53:38 Added: .RELEASE-PLAN-5.0.txt Log: - Add release plan draft for TC 5.0. Revision ChangesPath 1.1 jakarta-tomcat-5/RELEASE-PLAN-5.0.txt Index: RELEASE-PLAN-5.0.txt === $Id: RELEASE-PLAN-5.0.txt,v 1.1 2003/06/23 13:53:37 remm Exp $ Release Plan for Apache Tomcat 5.0 == Introduction: This document is a release plan for the final release of Apache Tomcat 5.0. The goal of the Apache Tomcat 5.0 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.4 and JSP 2.0 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.1.x releases. Apache Tomcat 5.0 includes the following major new features over Apache Tomcat 4.1: * Performance optimizations and reduced garbage collection * Refactored application deployer, with an optional standalone deployer allowing validation and compilation of a web application before putting it in production * Complete server monitoring using JMX and the manager web application * Scalability and reliability enhancements * Improved Taglibs handling, including advanced pooling and tag plugins * Improved platform integration, with native Windows and Unix wrappers * Embedding of Tomcat using JMX * Expanded documentation Apache Tomcat 5.0 will use the build numbering and release process first used in the Apache HTTPd 2.0.x project. Milestone builds, numbered 5.0.x, will be released as needed and will recieve a stability rating after a one week testing period. The rating can be either: Alpha, Beta, or Stable. This Release Plan proposes the following prospective target dates for stability: End of July, 2003 - Tomcat 5.0 should reach Beta status. Servlet 2.4 and JSP 2.0 Final Specification Releases (expected by 09/2003) At least another Beta rated release should be made simultaneous to the release of the specification. Two to four weeks after Final Specification Releases Best effort should be made for Tomcat 5.0 to reach Stable status as soon as possible after the specification releases. However, it should be pointed out that wide testing cannot occur before the specifications are released, so a Stable release should only be made after a period of time. In order to complete a first Stable release, all outstanding Bugzilla bug reports against Tomcat 5.0 above NORMAL severity need to be fixed or deferred for later releases. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their severity accordingly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.0] Draft release plan
Hi, I have committed a rather generic release plan draft for TC 5.0. I have no problem trying to shorten the release cycle if people want to (but then, some people will have to step up and get their hands dirty contributing to the docs and fixing bugs). Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21010] - Error creating new context
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=21010. 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=21010 Error creating new context --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 14:05 --- Actually, small correction: this doesn't happen in TC 4.1.x, as it doesn't try to save the context stuff as separate files. I'll slightly refactor things and expose a config file base field at the host level, and add escaping code in StandardContext. This should fix the issue, as well as bug 19607. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 21018] New: - CharConversionException
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=21018. 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=21018 CharConversionException Summary: CharConversionException Product: Tomcat 4 Version: 4.1.24 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote HTTP/1.1 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If I have a %25 as part of the request (%25 is the percent sign), I get this exception: java.io.CharConversionException: EOF at org.apache.tomcat.util.buf.UDecoder.convert(UDecoder.java:119) at org.apache.tomcat.util.buf.UDecoder.convert(UDecoder.java:87) at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:408) at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:495) at org.apache.tomcat.util.http.Parameters.handleQueryParameters(Parameters.java:278) at org.apache.coyote.tomcat4.CoyoteRequest.parseRequestParameters(CoyoteRequest.java:1933) at org.apache.coyote.tomcat4.CoyoteRequest.getParameter(CoyoteRequest.java:911) at org.apache.coyote.tomcat4.CoyoteRequestFacade.getParameter(CoyoteRequestFacade.java:178) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1062) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/security SecurityClassLoad.java
jfarcand2003/06/23 12:22:26 Modified:catalina/src/share/org/apache/catalina/security SecurityClassLoad.java Log: Put the method call under the proper method :-) Revision ChangesPath 1.9 +7 -7 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/security/SecurityClassLoad.java Index: SecurityClassLoad.java === RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/security/SecurityClassLoad.java,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- SecurityClassLoad.java23 Jun 2003 19:14:41 - 1.8 +++ SecurityClassLoad.java23 Jun 2003 19:22:26 - 1.9 @@ -116,9 +116,6 @@ loader.loadClass (basePackage + loader.WebappClassLoader$PrivilegedFindResource); -loader.loadClass -(basePackage + - session.StandardManager$PrivilegedDoUnload); } @@ -130,6 +127,9 @@ loader.loadClass (basePackage + session.StandardSession$1); +loader.loadClass +(basePackage + + session.StandardManager$PrivilegedDoUnload); } - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/security - New directory
jfarcand2003/06/23 12:33:09 jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/security - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/security SecurityClassLoad.java
jfarcand2003/06/23 12:35:59
Modified:jasper2 build.xml
jasper2/src/share/org/apache/jasper/compiler
JspRuntimeContext.java
Added: jasper2/src/share/org/apache/jasper/security
SecurityClassLoad.java
Log:
Refactorize the way inner classes are loaded when the security manager is turned on.
Add a security folder and start moving all security related code into that folder
(same design as org.apache.catalina). Add inner classes required to be loaded at
startup.
Revision ChangesPath
1.23 +1 -0 jakarta-tomcat-jasper/jasper2/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/build.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- build.xml 12 Mar 2003 20:28:23 - 1.22
+++ build.xml 23 Jun 2003 19:35:59 - 1.23
@@ -157,6 +157,7 @@
include name=org/apache/jasper/compiler/Localizer.class /
include name=org/apache/jasper/resources/** /
include name=org/apache/jasper/runtime/** /
+include name=org/apache/jasper/security/** /
include name=org/apache/jasper/util/** /
/fileset
/jar
1.15 +6 -41
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspRuntimeContext.java
Index: JspRuntimeContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspRuntimeContext.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- JspRuntimeContext.java29 May 2003 16:34:37 - 1.14
+++ JspRuntimeContext.java23 Jun 2003 19:35:59 - 1.15
@@ -85,6 +85,7 @@
import org.apache.jasper.JspCompilationContext;
import org.apache.jasper.Options;
import org.apache.jasper.runtime.JspFactoryImpl;
+import org.apache.jasper.security.SecurityClassLoad;
import org.apache.jasper.servlet.JspServletWrapper;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
@@ -113,43 +114,7 @@
*/
static {
JspFactoryImpl factory = new JspFactoryImpl();
-if( System.getSecurityManager() != null ) {
-String basePackage = org.apache.jasper.;
-try {
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspFactoryImpl$PrivilegedGetPageContext);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspFactoryImpl$PrivilegedReleasePageContext);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspRuntimeLibrary);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspRuntimeLibrary$PrivilegedIntrospectHelper);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.ServletResponseWrapperInclude);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.TagHandlerPool);
-factory.getClass().getClassLoader().loadClass( basePackage +
-servlet.JspServletWrapper);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspFragmentHelper);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.ProtectedFunctionMapper);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.ProtectedFunctionMapper$1);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.ProtectedFunctionMapper$2);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.PageContextImpl);
- factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.PageContextImpl$1);
-factory.getClass().getClassLoader().loadClass( basePackage +
-runtime.JspContextWrapper);
-} catch (ClassNotFoundException ex) {
-System.out.println(
-Jasper JspRuntimeContext preload of class failed: +
-ex.getMessage());
-}
-}
+SecurityClassLoad.securityClassLoad(factory.getClass().getClassLoader());
JspFactory.setDefaultFactory(factory);
}
1.1
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/security/SecurityClassLoad.java
Index: SecurityClassLoad.java
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core StandardHostDeployer.java
remm2003/06/23 13:33:27
Modified:catalina/src/share/org/apache/catalina/core
StandardHostDeployer.java
Log:
- Code cleanup.
- Remove XML descriptor on undeploy (bug 19607).
Revision ChangesPath
1.12 +16 -9
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardHostDeployer.java
Index: StandardHostDeployer.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardHostDeployer.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- StandardHostDeployer.java 21 Jun 2003 20:00:23 - 1.11
+++ StandardHostDeployer.java 23 Jun 2003 20:33:27 - 1.12
@@ -128,6 +128,7 @@
*/
private ContextRuleSet contextRuleSet = null;
+
/**
* The codeDigester/code instance to use for deploying web applications
* to this codeHost/code. strongWARNING/strong - Usage of this
@@ -136,6 +137,7 @@
*/
private Digester digester = null;
+
/**
* The codeStandardHost/code instance we are associated with.
*/
@@ -411,7 +413,7 @@
// save context info into configFile
Engine engine = (Engine)host.getParent();
StandardServer server = (StandardServer)
engine.getService().getServer();
-server.storeContext(context);
+//server.storeContext(context);
} catch (Exception e) {
log.error(sm.getString(standardHost.installError, contextPath),
e);
@@ -629,8 +631,10 @@
host.log(sm.getString(standardHost.removing, contextPath));
try {
// Get the work directory for the Context
-File workDir = (File)
-context.getServletContext().getAttribute(Globals.WORK_DIR_ATTR);
+File workDir =
+(File) context.getServletContext().getAttribute
+(Globals.WORK_DIR_ATTR);
+String configFile = context.getConfigFile();
host.removeChild(context);
if (undeploy) {
@@ -645,7 +649,8 @@
host.getAppBase());
File contextFile = new File(context.getDocBase());
File baseDir = contextFile.getParentFile();
-if (appBase.getCanonicalPath().equals(baseDir.getCanonicalPath())) {
+if (appBase.getCanonicalPath().equals
+(baseDir.getCanonicalPath())) {
isAppBase = true;
}
@@ -655,7 +660,8 @@
}
// Only remove directory and/or war if they are located in the
// Host's appBase and autoDeploy or liveDeploy are true
-if (isAppBase (host.getAutoDeploy() || host.getLiveDeploy())) {
+if (isAppBase
+(host.getAutoDeploy() || host.getLiveDeploy())) {
String filename = contextFile.getName();
if (isWAR) {
filename = filename.substring(0,filename.length()-4);
@@ -669,7 +675,8 @@
deleteDir(contextFile);
}
if (host.isUnpackWARs()) {
-File contextWAR = new File(context.getDocBase() +
.war);
+File contextWAR =
+new File(context.getDocBase() + .war);
if (contextWAR.exists()) {
if (contextLastModified
contextWAR.lastModified()) {
@@ -681,8 +688,8 @@
contextFile.delete();
}
}
-if (host.isDeployXML()) {
-File docBaseXml = new File(appBase,filename + .xml);
+if (host.isDeployXML() (configFile != null)) {
+File docBaseXml = new File(configFile);
docBaseXml.delete();
}
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 19607] - ant undeploy only stops the Context, but doesn't remove physial files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19607. 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=19607 ant undeploy only stops the Context, but doesn't remove physial files [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 20:51 --- This is fixed in CVS, as part of the deployer refactorings. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader WebappLoader.java
remm2003/06/23 14:44:32
Modified:catalina/src/share/org/apache/catalina/loader
WebappLoader.java
Log:
- Add logging on initialization of the URL stream handler.
Revision ChangesPath
1.19 +30 -9
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader/WebappLoader.java
Index: WebappLoader.java
===
RCS file:
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader/WebappLoader.java,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- WebappLoader.java 20 Jun 2003 21:39:13 - 1.18
+++ WebappLoader.java 23 Jun 2003 21:44:32 - 1.19
@@ -164,6 +164,12 @@
/**
+ * First load of the class.
+ */
+private static boolean first = true;
+
+
+/**
* The class loader being managed by this Loader component.
*/
private WebappClassLoader classLoader = null;
@@ -253,11 +259,18 @@
protected PropertyChangeSupport support = new PropertyChangeSupport(this);
-// Classpath set in the loader
-private String classpath=null;
+/**
+ * Classpath set in the loader.
+ */
+private String classpath = null;
+
+
+/**
+ * Repositories that are set in the loader, for JMX.
+ */
+private ArrayList loaderRepositories = null;
+
-// repositories that are set in the loader, for jmx
-private ArrayList loaderRepositories;
// - Properties
@@ -690,10 +703,18 @@
// Register a stream handler factory for the JNDI protocol
URLStreamHandlerFactory streamHandlerFactory =
new DirContextURLStreamHandlerFactory();
-try {
-URL.setURLStreamHandlerFactory(streamHandlerFactory);
-} catch (Throwable t) {
-// Ignore the error here.
+if (first) {
+first = false;
+try {
+URL.setURLStreamHandlerFactory(streamHandlerFactory);
+} catch (Exception e) {
+// Log and continue anyway, this is not critical
+log.error(Error registering jndi stream handler, e);
+} catch (Throwable t) {
+// This is likely a dual registration
+log.info(Dual registration of jndi stream handler:
+ + t.getMessage());
+}
}
// Construct a class loader based on our current repositories list
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk multiple slashes reveals jsp code
Hi, When using mod_jk and apache13: JkMount /app/*jsp ajp13 will redirect requests like http://server/app/foobar.jsp to tomcat, just fine. But, http://server//app/foobar.jsp will not be catched by JkMount, and apache will send the jsp source code to the browser. Of course, a rewrite can hinder this, but is it really meant to be this way? Is it just me having problems? /Palle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler Generator.java
kinman 2003/06/23 16:20:45
Modified:jasper2/src/share/org/apache/jasper/compiler Generator.java
Log:
- Allow the value attrbute of jsp:param action be non String types.
Revision ChangesPath
1.189 +14 -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.188
retrieving revision 1.189
diff -u -r1.188 -r1.189
--- Generator.java24 May 2003 00:53:09 - 1.188
+++ Generator.java23 Jun 2003 23:20:44 - 1.189
@@ -709,16 +709,19 @@
if (!attr.isNamedAttribute() (v == null))
return ;
-if (attr.isExpression() || attr.isELInterpreterInput()) {
- if (attr.isELInterpreterInput()) {
- boolean replaceESC = v.indexOf(Constants.ESC) 0;
- v = JspUtil.interpreterCall(this.isTagFile,
+if (attr.isExpression()){
+ if (encode) {
+ return
org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode(String.valueOf( + v + ),
request.getCharacterEncoding());
+ }
+ return v;
+ } else if (attr.isELInterpreterInput()) {
+ boolean replaceESC = v.indexOf(Constants.ESC) 0;
+ v = JspUtil.interpreterCall(this.isTagFile,
v, expectedType,
attr.getEL().getMapName(), false );
- // XXX ESC replacement hack
- if (replaceESC) {
- v = ( + v + ).replace( + Constants.ESCStr + , '$');
- }
+ // XXX ESC replacement hack
+ if (replaceESC) {
+ v = ( + v + ).replace( + Constants.ESCStr + , '$');
}
if (encode) {
return org.apache.jasper.runtime.JspRuntimeLibrary.URLEncode( +
v + , request.getCharacterEncoding());
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: jakarta-tomcat-site/docs/faq/printer version.html misc.html connectors.html classnotfound.html
funkman 2003/06/23 19:07:02 Modified:xdocs-faq version.xml misc.xml connectors.xml classnotfound.xml docs/faq version.html misc.html connectors.html classnotfound.html docs/faq/printer version.html misc.html connectors.html classnotfound.html Log: FAQ update, added questions: - When is the next release? - Tagpool.release - jk2 link - java.lang.NoClassDefFoundError help - Fixed minor formatting In my diff - lots of html showed as changed - not sure why yet. Sorry for the big email commit message. Revision ChangesPath 1.2 +22 -3 jakarta-tomcat-site/xdocs-faq/version.xml Index: version.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/version.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- version.xml 12 Jun 2003 00:31:14 - 1.1 +++ version.xml 24 Jun 2003 02:07:01 - 1.2 @@ -25,9 +25,17 @@ section name=Questions ul - lia href=#which -Which tomcat version should I use? - /a /li + li + a href=#which + Which tomcat version should I use? + /a + /li + + li + a href=#when +When will the next version be released? + /a + /li /ul /section @@ -66,6 +74,17 @@ tomcat home page /a should have the correct recommendation. /answer + +question + a name=when +When will the next version be released? + /a +/question +answer + a href=http://marc.theaimsgroup.com/?l=tomcat-useramp;m=102351104906437amp;w=2; +When it is ready. + /a +/answer /section 1.2 +21 -2 jakarta-tomcat-site/xdocs-faq/misc.xml Index: misc.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/misc.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- misc.xml 12 Jun 2003 00:31:14 - 1.1 +++ misc.xml 24 Jun 2003 02:07:01 - 1.2 @@ -111,7 +111,11 @@ from a servlet? (or jsp) /a /li - +li + a href=#tagbroken +Is tag pooling broken? It doesn't call release! + /a +/li /ul /p @@ -312,7 +316,7 @@ question -a name=properties +a name=error How do I get a customized error page? /a /question @@ -473,6 +477,21 @@ header. /answer + + + question + a name=#tagbroken +Is tag pooling broken? It doesn't call release! + /a + /question + answer +It is not broken, your tag probably is. Many bug reports +have been filed about this. + a href=http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16001; +Here + /a +is the bug report with all the gory details. + /answer 1.2 +6 -0 jakarta-tomcat-site/xdocs-faq/connectors.xml Index: connectors.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/connectors.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- connectors.xml12 Jun 2003 00:31:14 - 1.1 +++ connectors.xml24 Jun 2003 02:07:01 - 1.2 @@ -58,6 +58,12 @@ /a /li + li[link] +a href=http://www.greenfieldresearch.ca/technical/jk2_config.html; + Tomcat-Apache using JK2 connector +/a + /li + li[thread] a href=http://marc.theaimsgroup.com/?t=10404005824amp;r=1amp;w=2; Configuring mod_jk - Again! 1.2 +20 -0 jakarta-tomcat-site/xdocs-faq/classnotfound.xml Index: classnotfound.xml === RCS file: /home/cvs/jakarta-tomcat-site/xdocs-faq/classnotfound.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- classnotfound.xml 12 Jun 2003 00:31:14 - 1.1 +++ classnotfound.xml 24 Jun 2003 02:07:01 - 1.2 @@ -62,6 +62,9 @@ /a /li /ul +If you get a +codeNoClassDefFoundError/code exception, the root might be the +same reason as a codeClassNotFound/code exception. /section section name=Questions @@ -76,6 +79,11 @@ javax/servlet/Filter/code /a /li +li + a href=#xml +Why do I get codeNoClassDefFoundError: org/xml/sax/InputSource/code? +/a + /li /ul /p /section @@ -115,6 +123,18 @@ This really messes up the classloaders since Tomcat's classloaders don't act quite as normal as
Re: [5.0] Draft release plan
Remy Maucherat wrote: Hi, I have committed a rather generic release plan draft for TC 5.0. I have no problem trying to shorten the release cycle if people want to (but then, some people will have to step up and get their hands dirty contributing to the docs and fixing bugs). I doubt I can do anything usefull for the next 2-3 months... Sorry :-( I'll try to find some time to read the dev list, and I may get few hours per week. Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
