Actually, if I am not mistaken, the attached txt file patches the
problem. An IntrospectionHelper.setProperty was needed for allowTrace.
On 5.0.x this was done automatically by setting a property in the
setAllowTrace setter. Then the properties were set into
IntrospectionHelper en masse later.
This patch works for me, at least.
Attached: patch.txt
[EMAIL PROTECTED] 2/27/04 1:13:02 PM
When I browse to a Coyote Connector in Tomcat's admin in 4.1.30, I get
an HTTP 500 error - Error retrieving attribute allowTrace. I know
the
allowTrace functionality was added about a month ago, and was not a
required attribute on the connector.
This functionality works in Tomcat 5.0.19, but not 4.1.30
Jeff Tulley ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jeff Tulley ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
Index: org/apache/coyote/tomcat4/CoyoteConnector.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat4/CoyoteConnector.java,v
retrieving revision 1.34
diff -u -r1.34 CoyoteConnector.java
--- org/apache/coyote/tomcat4/CoyoteConnector.java 24 Feb 2004 08:54:29 -
1.34
+++ org/apache/coyote/tomcat4/CoyoteConnector.java 27 Feb 2004 20:45:01 -
@@ -1198,6 +1198,8 @@
+ tomcatAuthentication);
IntrospectionUtils.setProperty(protocolHandler, compression,
compression);
+IntrospectionUtils.setProperty(protocolHandler, allowTrace,
++ allowTrace);
if (address != null) {
IntrospectionUtils.setProperty(protocolHandler, address,
address);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
