The async thing is nice; that would be a good thing to bring into S2. I still don't like the string-based action returns; strings are just awful. I don't have a better solution (yet).
It might be a good time for me to rethink the code-based config I'd implemented some time ago, e.g., use a Groovy or whatever DSL to config the results, that way they end up being code artifacts. On Mon, Jan 25, 2016 at 8:49 AM, Christoph Nenning < christoph.nenn...@lex-com.net> wrote: > > Hi folks, > > > > has anyone seen this before? > > http://jodd.org/doc/madvoc/index.html > > > > Looks like they are taking basic Struts 2 concepts and mixing it with > > some Spring MVC and Seam. > > > > It might be interesting to evaluate which of their concepts might be > > nice to integrate in S2.5/3 - just sayin' ... :) > > > > - René > > > > > It is heavily centered around annotations and convention. You can feel > that it has not "more than a decade" of history. To achieve that for > struts it would be necessary to delete half the code base ;) > > > Two things that popped to my eye: > - you can declare actions as async and thus use asyncContext from servlet > api 3.0 > - you can declare result type in string returned by action instead of > configuring it up front: > return "redirect:/<two>?value=${value}"; > > > > Regards, > Christoph > > This Email was scanned by Sophos Anti Virus > -- e: davelnew...@gmail.com m: 908-380-8699 s: davelnewton_skype t: @dave_newton <https://twitter.com/dave_newton> b: Bucky Bits <http://buckybits.blogspot.com/> g: davelnewton <https://github.com/davelnewton> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
