Sorry, bad assumption on my part. I was looking out for the 4.1.30 tag in jakarta-tomcat-4.0 and didn't realize that jakarta-tomcat-connectors had been tagged the day before.
Since a 4.1.31 isn't likely, I'll prepare a patch to correct this for 4.1.30. Cheers, Larry > -----Original Message----- > From: Jeff Tulley [mailto:[EMAIL PROTECTED] > Sent: Friday, February 27, 2004 6:07 PM > To: [EMAIL PROTECTED] > Subject: Re: allowTrace attribute causing problemsin the > adminapplication > > > Yeah, that's what it looked like. Larry's backport of the > "allowTrace" > stuff in the connector code came after the TOMCAT_4_1_30 tag, > whereas in > the admin application, the file that wanted to look for the > allowTrace, > in EditConnectorAction.java WAS tagged with 4.1.30 > > >>> [EMAIL PROTECTED] 2/27/04 4:03:38 PM >>> > K. I can reproduce the problem with 4.1.30 build but not in the > workspace. > Looks like the latest org.apache.coyote.tomcat4.CoyoteConnector with > allowTrace didn't get tagged for 4.1.30. 4.1.30 tag has outdated > o.a.c.tomcat4.CoyoteConnector.... > > Amy > > > --------------------------------------------------------------------- > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
