----- Original Message -----
From: "Pierre Delisle" <[EMAIL PROTECTED]>
> The JSP spec is quite clear on the subject:
>
> "The only types of properties that can be assigned to from String
> constants and request parameter values are those listed in TABLE 2-4; the
conversion applied
> is that shown in the table. Request-time expressions can be assigned to
properties of any
> type; no automatic conversions will be performed."
>
> boolean or Boolean As indicated in java.lang.Boolean.valueOf(String)
> byte or Byte As indicated in java.lang.Byte.valueOf(String)
> char or Character As indicated in java.lang.Character.valueOf(String)1
> double or Double As indicated in java.lang.Double.valueOf(String)
> int or Integer As indicated in java.lang.Integer.valueOf(String)
> float or Float As indicated in java.lang.Float.valueOf(String)
> long or Long As indicated in java.lang.Long.valueOf(String)
>
> [Please note that short/Short is missing from the list].
>
> We had a discussion on the topic sometimes this summer (if you look at
> the archives). Also seems to me that this would make sense.
I've tried to search the list archive (the search message feature is down,
so I had to manually search the subjects for "tag"), and I found the
discussion you had with Arun Re: Spec Q/TagBeginGenerator behavior. He
layed out the same issue, and your response was that you would forward it to
the JSP spec group. I can't find any resolution message.
<ornery>
Anyway, it seems you've made your mind or received work from the JSP spec
group and I can't find the response.
Consider this one point though... I'm reading over the JLS as to what
exactly a "conversion" is... I'm probably misreading this, but it seems to
say that passing the String constant to the String setter method involves
the "identity" conversion and passing the String constant to the Object
setter method is a "widening reference" conversion. (a note about widening
conventions: "Such conversions never require a special action at run time
and therefore never throw an exception at run time.") Given TABLE 2-4 does
not list either how to handle String's identity or Object's widening
conversion to the Object setter method, why support one but not the other?
</ornery>
> Let me try to ping the spec lead on this to see if we could get
> final resolution.
Thanks very much appreciated (please take my orneriness as amusement if
nothing else). I'll harass Eduardo as well if it will help.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
