Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3974B3DE.31D95EB@eng.sun.com>
Date: Tue, 18 Jul 2000 12:45:34 -0700
From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: Jasper code generation problem (bug?)
References: <4.2.2.20000717143637.00afd160@facstaff.wisc.edu>
 <3973968B.FCD052D9@mcnerthney.com> <3974DBF9.5E5DC687@mcnerthney.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Patrick J. McNerthney" wrote:

> Did I submit this question to the right place?

This does turn out to be a bug in Tomcat.  I'm not sure it can get
addressed
in a 3.2 timeframe, but will definitely be addressed in a subsequent
version.

Craig McClanahan


>
> "Patrick J. McNerthney" wrote:
> >
> > When I create a custom tag with a name that contains a dash, such as
> > "Foo-Bar", Jasper uses this name in the generation of the variable name
> > used to hold the instance of this tag.  Since the dash is not a valid
> > java variable character, this code does not compile under javac.  Other
> > JSP compilers, such as WebLogic do handle tag names with dashes fine.
> >
> > The JavaServer Pages Specification, Version 1.1 states in section 5.3.5
> > that the name element's PCDATA is comprised of NMTOKEN (name token),
> > which according to the XML specification includes the dash.
> >
> > Is this a problem with Jasper or does the JSP specification in fact
> > preclude the use of dashes in the name element PCDATA?
> >
> > Thanks,
> > Pat McNerthney
> > Icicle Software, Inc.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org