[
https://issues.apache.org/jira/browse/WW-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764320#comment-13764320
]
mahendran commented on WW-4188:
-------------------------------
For html5 compatibility, they (apache)should introduce a new attribute by the
name "mandatory". This makes the every one to understand clear also provides
backward compatibility. Hope apache realize the importance of backward
compatibility soon as many applications are ending up with same problem and
knocking their door for solution. :) :)
> In struts tag lib, required attribute removed in latest version ie 2.3.15.1
> ---------------------------------------------------------------------------
>
> Key: WW-4188
> URL: https://issues.apache.org/jira/browse/WW-4188
> Project: Struts 2
> Issue Type: Improvement
> Components: Other
> Affects Versions: 2.3.15.1
> Environment: All
> Reporter: mahendran
> Assignee: Lukasz Lenart
> Priority: Blocker
> Labels: struts-tags-required-attribute
> Fix For: 2.3.16
>
>
> we are using struts 2.0.5 and 2.3.4.1 in our applications. And we decided to
> migrate to 2.3.15.1 to get the security fixes.
> we use struts tags to render UI components and using 'required' attribute to
> get the '*' along with the components.
> In the version 2.3.15.1, the attribute required is dropped, and we need to
> change to requiredLabel to get the same effect, this increases
> migration&testing effort for a application which has 1000+pages
> Hence we require a backward compatibility for 'required' attribute in struts
> tags.
> Also nowhere in the migration document this information is specified. This
> makes the struts migration as block-box. Hence we require a proper migration
> document which should specify what are all the changes required in the
> application to migrate the struts.
> But we managed to get the '*' in UI by replacing
> UIBean.class,AbsctactUITag.class and struts.tld from 2.3.4.1 version.
--
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
