struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rene Gielen (JIRA)" <>
Subject [jira] [Commented] (WW-4188) In struts tag lib, required attribute removed in latest version ie
Date Fri, 07 Nov 2014 09:44:34 GMT


Rene Gielen commented on WW-4188:

[~mahendranmahesh] Thanks for your report and your suggestions. To clarify, please be aware
that when skipping multiple releases for upgrading, you will have to follow the version and
migration notes for each intermediate release up to your target version.

Please also understand that this is public benefit Open Source with volunteers working for
free on the project. There is nothing like "requiring" to have them change something. This
is an option you might get from a commercial product with paid SLAs, though even this is usually
not guaranteed. In turn, our volunteers are always open to users humbly asking for a change
- something you might not get from every commercial product :)

> In struts tag lib, required attribute removed in latest version ie
> ---------------------------------------------------------------------------
>                 Key: WW-4188
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Other
>    Affects Versions:
>         Environment: All
>            Reporter: mahendran
>            Assignee: Lukasz Lenart
>              Labels: struts-tags-required-attribute
>             Fix For: 2.5
> we are using struts 2.0.5 and in our applications. And we decided to migrate
to 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, 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 version.

This message was sent by Atlassian JIRA

View raw message