Mailing-List: contact issues-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@struts.apache.org
Date: Thu, 5 Sep 2013 07:18:51 +0000 (UTC)
From: "mahendran (JIRA)" <jira@apache.org>
To: issues@struts.apache.org
Message-ID: <JIRA.12667056.1378364983018.83574.1378365531585@arcas>
In-Reply-To: <JIRA.12667056.1378364983018@arcas>
References: <JIRA.12667056.1378364983018@arcas>
Subject: [jira] [Updated] (WW-4188) In struts tag lib, required attribute
 removed in latest version ie 2.3.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/WW-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mahendran updated WW-4188:
--------------------------

    Description: 
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.

  was:
we are using struts 2.0.5 and 2.3.4.1 in our applications. nd 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.

    
> 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
>            Priority: Blocker
>              Labels: struts-tags-required-attribute
>
> 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