Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: allowTrace attribute causing problems in the adminapplication
Date: Fri, 27 Feb 2004 16:42:54 -0500
Message-ID: <8D966D6B75EB7F47AA300241BF2E1D0C01D1172E@merc17.na.sas.com>
Thread-Topic: allowTrace attribute causing problems in the adminapplication
Thread-Index: AcP9cwoQJwmztYA+QX2g1uJTtxE7pQABY9Uw
From: "Larry Isaacs" <Larry.Isaacs@sas.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>

Hi Jeff,

I tested this before the 4.1.30 release, and just retested it,
and it continues to work for me without your patch.  Since the
protocolHandler doesn't support the "allowTrace" property, the
setProperty() is unnecessary in Tomcat 5.0.x and shouldn't make
a difference in Tomcat 4.1.30.  It is safer to keep the
setProperty() in Tomcat 5 in case somebody cut & pastes the
setAllowTrace() method for some new property that does need it.

Maybe a restart magically made the problem disappear.  Does
your 4.1.30 consistently show this problem without your patch?

Cheers,
Larry

> -----Original Message-----
> From: Jeff Tulley [mailto:JTULLEY@novell.com]=20
> Sent: Friday, February 27, 2004 3:48 PM
> To: tomcat-dev@jakarta.apache.org
> Subject: Re: allowTrace attribute causing problems in the=20
> adminapplication
>=20
>=20
> Actually, if I am not mistaken, the attached txt file patches the
> problem.  An IntrospectionHelper.setProperty was needed for=20
> allowTrace.=20
> 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.
>=20
> This patch works for me, at least.
>=20
> Attached: patch.txt
>=20
> >>> JTULLEY@novell.com 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.
>=20
> This functionality works in Tomcat 5.0.19, but not 4.1.30
>=20
> Jeff Tulley  (jtulley@novell.com)
> (801)861-5322
> Novell, Inc., The Leading Provider of Net Business Solutions
> http://www.novell.com=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org=20
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org=20
>=20
>=20
> Jeff Tulley  (jtulley@novell.com)
> (801)861-5322
> Novell, Inc., The Leading Provider of Net Business Solutions
> http://www.novell.com
>=20

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org