----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> I'm afraid that I disagree with you about whether this change would be
spec
> compliant or not.
[good points trimmed]
> Thus, you also have a workaround. Assume you've got a custom tag "foo"
that has
> a property (of class java.lang.Object) named "bar". Your patch would
enable
> saying:
>
> <mytags:foo bar="abc"/>
>
> which the page compiler will currently complain about. However, the
following
> will work just fine (assuming you've defined this attribute to accept
runtime
> expressions:
>
> <mytags:foo bar='<%= "abc" %>'/>
>
> which accomplishes the same thing.
Thanks for shedding light the finer points of the spec... I definitely want
to make my tags so that they are upward compatible. As for the workaround,
I can't believe that's the desired way to write JSPs as envisioned by the
spec writers, and unfortunately my company has 4 sites up already with 150+
JSP pages that are using the tag in question... I'd rather correct the tag
class rather than those JSPs if at all possible.
> We can ask Eduardo (the spec lead for JSP) about this next week when he
returns
> from vacation, but the intent is pretty clear -- doing this conversion is
> explicitly illegal in JSP 1.2 -- so I'd prefer not to put this change into
> Tomcat 3.2.
Fair enough... hopefully Eduardo can shed some light on the matter. An
important note though is that my patch only "fixed" the behavior when using
jspc... Jasper servlet compiles the page without a problem, allowing me to
do:
<mytags:foo bar="abc" />
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. Anyway, seems that if spec compliance is an issue, we should
have Tomcat 3.2 be uniform in both jspc and the Jasper Servlet. 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.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
