Ok, thanks for the clarification. On Thu, Oct 31, 2024, 10:30 PM Kusal Kithul-Godage < kusal.kithulgod...@gmail.com> wrote:
> Hi Brian, > > This is indeed already available from Struts 6.4 using the following > configuration option: > struts.parameters.requireAnnotations=true > > Kind regards, > Kusal > > On Fri, Oct 25, 2024 at 2:24 PM Brian Andle <brianandle...@gmail.com> > wrote: > > > > I know off topic so sending directly. Should the @StrutsParameter > annotation, and just the annotation class, be backported to 6 as well? It > could/should be a no-op in 6.x but would let people start adding the > annotation ahead of the 7 upgrade? > > > > ---------- Forwarded message --------- > > From: Kusal Kithul-Godage <kusal.kithulgod...@gmail.com> > > Date: Thu, Oct 24, 2024, 9:35 PM > > Subject: Re: Package rename transition > > To: Struts Developers List <dev@struts.apache.org> > > > > > > These changes are all merged to master/6.x now - thanks Lukasz for > reviewing > > I'll sort out the merge conflicts with the 7.0 branch in a few days > > > > On Mon, Oct 21, 2024 at 5:52 PM Kusal Kithul-Godage > > <kusal.kithulgod...@gmail.com> wrote: > > > > > > So in Struts 7.0, the com.opensymphony.xwork2 package is being renamed > > > and merged with org.apache.struts2. > > > > > > For many applications this will be a straightforward find and replace > > > when upgrading to 7.0. However, I was doing some investigation into > > > whether we can provide a small deprecation/transitionary period where > > > both packages are supported (e.g. Struts 6.7). This would be very > > > helpful for migrating large multi-module codebases. > > > > > > After some work [1], I was able to get key APIs working in both > > > packages. With these changes, most Action, Result and Interceptor > > > classes can be migrated over to the new org.apache.struts2 namespace. > > > I've also created compatible org.apache.struts2 counterparts for > > > com.opensymphony.xwork2.ActionContext as well as a bunch of Action > > > marker interfaces. > > > > > > I've taken care to ensure these changes don't impact backwards > > > compatibility and so migrating to the new package namespace as part of > > > Struts 6.x is entirely optional. > > > > > > I'm not sure if there is another Struts 6.x release planned but I > > > think there's some value in providing such a transitional version, > > > even if it's only for a subset of APIs. Thoughts? > > > > > > [1] https://github.com/apache/struts/pulls/kusalk > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > For additional commands, e-mail: dev-h...@struts.apache.org > > >
