tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <Craig.McClana...@eng.sun.com>
Subject Re: Patch for bug report #362 (and a patch for a logging error)
Date Sat, 11 Nov 2000 00:41:24 GMT
Serge Knystautas wrote:

> [snip]
> The way I got this to work was to overload the setter method to take both a
> String and an Object... this got it working through Jasper Servlet but not
> jspc.  I don't know if that's a violation of the spec or the way to handle
> this issue.

Yep, it is, and again this is made explicit in JSP 1.2 :-(.

I was trying something similar (overloaded setters) originally with Struts, and
it went down in flames on most servlet containers because many of them just use
the standard JavaBeans introspector -- and the introspector returns a property
setter only if there is a single method.  On one of the other containers, you'd
start getting compiler errors like "this is a read-only property" because the
introspector returned neither setter.

>  Anyway, seems that if spec compliance is an issue, we should
> have Tomcat 3.2 be uniform in both jspc and the Jasper Servlet.

That is *definitely* true.  Unfortunately, I'm not the person most versed with
the JSP compiler.  Pierre Delisle is, and he will also be back on Monday.

>  I looked
> through the code some and didn't understand why it would compile from the
> Jasper Servlet but not jspc (before my patch), but that's what's happening
> for me with Tomcat 3.2b6.
>

I will look at this as well, and see if anything obvious stands out.

>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>

Craig



Mime
View raw message