You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Paul Benedict <pb...@apache.org> on 2014/11/09 03:23:12 UTC
Ideas for 3.0 (aka let's branch)
We should whiteboard on the wiki. Here are some things I had in mind:
* Target Java 7 and EE 6 minimum
* Refactor to clearly delineate framework externals (apis) and framework
internals
* Replace XWork annotations with Beans Validation annotations
* Replace XWork injection with CDI injection
* Full HTML 5 support
* Use annotations to configure actions
* Be a candidate for EE 8's JSR web framework spec
I also believe (and believe a debate will ensue)....
* We should make all plugins independent projects like Maven.
Cheers,
Paul
Re: Ideas for 3.0 (aka let's branch)
Posted by Lukasz Lenart <lu...@apache.org>.
2014-11-09 23:15 GMT+01:00 Paul Benedict <pb...@apache.org>:
> Whatever we choose to do, I would like to first work on rearranging the
> packages to make the api clear.
What do you need?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Ideas for 3.0 (aka let's branch)
Posted by Paul Benedict <pb...@apache.org>.
Whatever we choose to do, I would like to first work on rearranging the
packages to make the api clear.
On Nov 9, 2014 8:11 AM, "Lukasz Lenart" <lu...@apache.org> wrote:
> 2014-11-09 3:23 GMT+01:00 Paul Benedict <pb...@apache.org>:
> > We should whiteboard on the wiki. Here are some things I had in mind:
> >
> > * Target Java 7 and EE 6 minimum
> > * Refactor to clearly delineate framework externals (apis) and framework
> > internals
> > * Replace XWork annotations with Beans Validation annotations
>
> I would rather be agnostic here and allow use any validation mechanism
> you want this means API and SPI
>
> > * Replace XWork injection with CDI injection
>
> This is good but is it supported by every container?
>
> > * Full HTML 5 support
> > * Use annotations to configure actions
>
> Not sure what you mean - you can use annotations even now. What about
> convention? Also configuration via code or XML is also a good idea.
>
> > * Be a candidate for EE 8's JSR web framework spec
>
> You can add them here
> https://cwiki.apache.org/confluence/display/WW/Struts+Next
>
> > I also believe (and believe a debate will ensue)....
> > * We should make all plugins independent projects like Maven.
>
> I like that idea but have some doubts - not everybody is using Maven
> to manage dependencies and because of that we will have to keep some
> page with version matrix. Do you have any idea how to handle it?
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Ideas for 3.0 (aka let's branch)
Posted by Lukasz Lenart <lu...@apache.org>.
2014-11-09 3:23 GMT+01:00 Paul Benedict <pb...@apache.org>:
> We should whiteboard on the wiki. Here are some things I had in mind:
>
> * Target Java 7 and EE 6 minimum
> * Refactor to clearly delineate framework externals (apis) and framework
> internals
> * Replace XWork annotations with Beans Validation annotations
I would rather be agnostic here and allow use any validation mechanism
you want this means API and SPI
> * Replace XWork injection with CDI injection
This is good but is it supported by every container?
> * Full HTML 5 support
> * Use annotations to configure actions
Not sure what you mean - you can use annotations even now. What about
convention? Also configuration via code or XML is also a good idea.
> * Be a candidate for EE 8's JSR web framework spec
You can add them here
https://cwiki.apache.org/confluence/display/WW/Struts+Next
> I also believe (and believe a debate will ensue)....
> * We should make all plugins independent projects like Maven.
I like that idea but have some doubts - not everybody is using Maven
to manage dependencies and because of that we will have to keep some
page with version matrix. Do you have any idea how to handle it?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org