Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 5238 invoked from network); 25 Nov 1999 13:32:03 -0000 Received: from if0011.swisslife.ch (HELO if0010.swisslife.ch) (195.141.129.17) by apache.org with SMTP; 25 Nov 1999 13:32:03 -0000 Received: from if0010. (localhost [127.0.0.1]) by if0010.swisslife.ch (8.8.8/8.8.6) with SMTP id OAA20589 for ; Thu, 25 Nov 1999 14:31:31 +0100 (MET) Received: hidden Message-ID: From: Brush John To: "'tomcat-dev@jakarta.apache.org'" Subject: AW: error parsing custom tags without body Date: Thu, 25 Nov 1999 14:31:30 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Well, according to the specification (V1.1PR2), section 5.1.2. under = "Simple Actions" it is legitimate to have "no text between the start and end = tag", and there is no context in which this is not true. It is possible, = however, to specify in the tag library descriptor one of three values for "bodycontent", namely "tagdependent", "JSP" or "empty", but in every = case an empty body is always legal. Since an empty body is always in accordance with the standard, there = are really only two possibilities: 1. the tomcat project is using a different version of the standard than = I am, or 2. it's a bug John > -----Urspr=FCngliche Nachricht----- > Von: Stephane Boisson [SMTP:s.boisson@insyscom.fr] > Gesendet am: Donnerstag, 25. November 1999 14:18 > An: Brush John > Cc: 'tomcat-dev@jakarta.apache.org' > Betreff: Re: error parsing custom tags without body >=20 > Brush John wrotet : >=20 > > I've been playing around with custom tags, and I've noticed an > inexplicable > > error when parsing custom tags that have an empty body, if the = "empty > body" > > does not consist of at least one whitespace. Basically this works: > > > > > > > > > > and this works: > > > > > > > > but this doesn't > > > > >=20 > I got the same problems, even with something like > But it will work for every case if you turn off JVM verification for > Tomcat by > adding the option -Xverify:none to the java command line (this is the > option > for Java 2). > But that still looks to me like a strange bug (tomcat or tag code?) >=20 > Regards, >=20 > St=E9phane Boisson >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org