You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2003/01/09 20:05:53 UTC
DO NOT REPLY [Bug 15927] -
ClassCastException when using the StrutsTag with scriptlets
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15927>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15927
ClassCastException when using the StrutsTag with scriptlets
------- Additional Comments From dmkarr@earthlink.net 2003-01-09 19:05 -------
If this is really the case, then I can see many related issues in the bean,
html, logic, and tiles libraries (by doing a search for "getAttributeString".
This particular case in the "struts" tag is different from the others, as we
just need to change "getAttributeString()" to "getAttribute()". The value is
ignored, we just check to see if it HAS a value.
The rest of the changes related to this would be to change many "rtexprvalue"
settings from "true" to "false", because it appears that the value is needed at
compile time, and can't wait until runtime. I wouldn't expect this to break any
applications, as I would assume they couldn't have worked in the first place, if
they were using expression scriptlets for these attributes.
The most common case of this is the "id" attribute, which has "rtexprvalue" set
to "true" in most cases. If an expression scriptlet is really used for the
value, I would expect a similar error when it tries to create the "VariableInfo"
object.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>