[
https://issues.apache.org/jira/browse/WW-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727689#comment-13727689
]
Paul Benedict edited comment on WW-4166 at 8/2/13 2:00 PM:
-----------------------------------------------------------
Wouldn't a "class" property corresponds to getClass()/setClass() methods? I
don't think you can overloaded methods in the JavaBean spec since getClass() is
on every Object. You'll have to implement this first, I suppose, just to make
sure my concern is (in)valid.
was (Author: paul4christ79):
Wouldn't a "class" property corresponds to getClass()/setClass() methods? I
don't think you can overloaded methods in the JavaBean spec since getClass() is
on every Object.
> Allow "class" attribute on Struts tags
> --------------------------------------
>
> Key: WW-4166
> URL: https://issues.apache.org/jira/browse/WW-4166
> Project: Struts 2
> Issue Type: Improvement
> Components: Other
> Reporter: Eric Lentz
> Priority: Trivial
> Fix For: 2.3.17
>
>
> In building a JSP, and working on web related things outside of the Java
> environment, there are lots of tags which all receive the "class" attribute.
> The Struts developer must _remember_ to call the attribute cssClass instead.
> Typing muscle memory drives me to half of the time typing "class" instead,
> which leads to HTML which reads, 'class="class java.util.HashMap"'
> Why not just allow "class" like the rest of the HTML world? Why do we need to
> be different? I have a billion things to remember when web developing, this
> shouldn't be one of them.
> We don't even have to to deprecate or obsolete cssClass, just also allow
> "class"... please!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
