Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 17833 invoked from network); 16 Sep 2002 20:27:47 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Sep 2002 20:27:47 -0000 Received: (qmail 17818 invoked by uid 97); 16 Sep 2002 20:28:09 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 17802 invoked by uid 97); 16 Sep 2002 20:28:08 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 17790 invoked by uid 98); 16 Sep 2002 20:28:08 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: tomcat 4.1.10 mishandling nested variables in tags? Date: Mon, 16 Sep 2002 16:27:28 -0400 Message-ID: <66337F04F2A1E440BF87F2080B5F5370623F79@madison.dc.Blackboard.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: tomcat 4.1.10 mishandling nested variables in tags? Thread-Index: AcJafWbDWLPQvyCyRhinnBPlmZUgyQDQbL3g From: "Tim Moore" To: "Tomcat Users List" X-OriginalArrivalTime: 16 Sep 2002 20:27:29.0057 (UTC) FILETIME=[7A3A4110:01C25DBF] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This workaround doesn't solve the problem for me. In the generated = classes for my JSPs, my scripting variable is only being set after = doAfterBody is called on the tag handler (with pooling either enabled or = disabled) even though the scripting variable scope is set to NESTED. = This all worked OK w/ TC 3.3.x. --=20 Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 > -----Original Message----- > From: Jacob Heric [mailto:jheric@Emery-Waterhouse.com]=20 > Sent: Thursday, September 12, 2002 12:53 PM > To: 'Tomcat Users List' > Subject: RE: tomcat 4.1.10 mishandling nested variables in tags? >=20 >=20 >=20 > I upgraded to 4.1.10 and got some similar, strange=20 > behaviour with variables in my tags showing up=20 > null. =20 >=20 > Here is the work around I used: >=20 > I disabled tag handler pooling on the jsp page compiler=20 > in the global web.xml file as follows: >=20 > at $CATALINA_BASE/conf/web.xml I added: >=20 > > jsp > =20 > org.apache.jasper.servlet.JspServlet > > logVerbosityLevel > DEBUG > > > enablePooling > false > =20 > 3 > >=20 > I am no longer having any problems with my tag libs. >=20 > Jacob >=20 >=20 > -----Original Message----- > From: Daniel Schmid [mailto:dschmid@avguide.ch] > Sent: Thursday, September 12, 2002 12:46 PM > To: 'Tomcat Users List' > Subject: AW: tomcat 4.1.10 mishandling nested variables in tags? >=20 >=20 > Is exactly the same for me. >=20 > I work with includes in the index.jsp. All the included=20 > template which uses a tag seem to make troubles in 4.1.10.=20 > the same app works like a charm in 4.0.4 with jasper 1. >=20 > Daniel Schmid >=20 > > -----Urspr=FCngliche Nachricht----- > > Von: Dave Townsend [mailto:dave.townsend@bigfoot.com] > > Gesendet: Donnerstag, 12. September 2002 15:49 > > An: tomcat-user@jakarta.apache.org > > Betreff: tomcat 4.1.10 mishandling nested variables in tags? > >=20 > >=20 > > Just upgraded to 4.1.10 and found that my webapp no longer > > functions. I have tracked this down to a tag that uses nested=20 > > tags. On the old version (4.0.4), immediately after the=20 > > doStartTag call, the variables are declared for the jsp page,=20 > > and their values read from the pageContext, then the jsp=20 > > content of the tag is executed. On the new version after the=20 > > doStartTag, the variables are declared and set to null and=20 > > only have their values updated after the jsp content has been=20 > > executed once. This means that all the variables are null on=20 > > the first run through the tag which as far as I understand=20 > > the spec is not correct. > >=20 > > Is there any fix for this? > >=20 > > Dave > >=20 > > -- > > "To successfully keep robbers out of your house put six locks > > on your door. When you go out, lock every other one. No=20 > > matter how long somebody stands there picking the locks, they=20 > > are always locking three." -- To unsubscribe, e-mail: For additional commands, e-mail: