--- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, 19 Mar 2001, Marc Saegesser wrote:
>
> >
> > This question comes a bug (387) against Tomcat-3.
> The JSP specification
> > defines tag names attribute names as containing
> NMTOKEN values. The
> > specification does not define NMTOKEN so I assume
> that the XML definition
> > applies. The XML definition of NMTOKEN allows
> strings that are not valid
> > Java identifiers.
>
> > Attribute names, however, pose a different
> problem. Attribute names map
> > into Java method names and thus can't contain some
> of NMTOKEN characters.
> > Either the specification should define a mapping
> of NMTOKEN values into Java
> > identifers or state that attribute names must be
> valid Java identifier
> > names.
> >
>
> It seems to me that Jasper should be using the
> standard JavaBeans
> introspection mechanisms to decide what actual
> setter method to call
> (instead of just gluing "set" on the front of the
> property name and fixing
> the capitalization). If it does so, the tag
> developer can use a BeanInfo
> class associated with their tag to map non-standard
> property names into
> the names of legal getter and/or setter methods.
>
I suppose this same could be said about our
interpretation of attributes in other places in the
code, such as for Intercepters, etc. In tc3.0, we can
probably address this all at once inside the
org.apache.tomcat.util.IntrospectionUtils class.
I believe jasper already depends on tomcat_util.jar so
this shouldn't introduce any new deployment
dependency.
mel
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
