One of my clients will take a LOT of "convincing" as they have 70 major
projects using Struts 2, and all use parameteraware.
Louis
Dr. Louis Smith, ThD
Chief Technology Officer, Kyra Solutions, Inc.
On Thu, Oct 6, 2016 at 4:27 AM, Lukasz Lenart <lukaszlen...@apache.org>
wrote:
> 2016-10-06 10:20 GMT+02:00 Lukasz Lenart <lukaszlen...@apache.org>:
> > 2016-10-06 10:17 GMT+02:00 Christoph Nenning <
> christoph.nenn...@lex-com.net>:
> >>> > For the HttpParameters ParameterAware change
> >>> >
> >>> > private Map<String, Object> params = Collections.emptyMap();
> >>> > ...
> >>> > setParameters(HttpParameters parameters) {
> >>> > this.params = parameters.toMap();
> >>> > }
> >>> >
> >>> > and use as before? (although it was a String, String[]).
> >>>
> >>> Hm... good point, maybe it makes sense revert it back to "String,
> >>> String[]" to avoid conflicts and add a new interface when you want to
> >>> use HttpParameters, wdyt?
> >>>
> >>>
> >>
> >> Yes, sounds like a good idea to have some kind of step-by-step migration
> >> for such a change.
> >>
> >> On the other side: we need to convince users to enable it and need some
> >> plan how and when to make it the default.
> >
> > Marking current interface as deprecated should be enough. In Struts
> > 2.6 we can drop it.
>
> If no objections I will drop the current test build and will introduce
> the above changes and then prepare a new test build
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>
