Christian, I agree on the "awful" documentation part. The S1 documentation
is better organized than S2. I thank everyone who wrote S2 documentation,
but it is incredibly difficult to sift through to find an answer. The wiki
may not be the right tool for the documentation although I don't have an
alternative except HTML files in SVN (like S1). If we can do anything to
make it more readable (even correcting the font and font size), I am all
for it.


On Wed, Sep 4, 2013 at 12:32 PM, Christian Grobmeier <grobme...@gmail.com>wrote:

> Comparison of web frameworks:
>
>
> http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/
>
> Lot of the things this guy said on Struts isn't accurate.
> A few things are worth to think about it:
>
> Quote:
>
> "Many devs see Struts as a legacy technology, so don’t expect fancy code
> generation in the place of boilerplate code. You need to configure a lot
> to start prototyping. An example project can be a good starting point.
> Something on the bright side: Struts has a Convention plugin, that
> enforces some convention over configuration and provides annotations to
> configure URL mappings and some other stuff. This should speed up things
> a bit.
>
> Score: 2/5 – Lots of boilerplate code, no built-in code generation, no
> external powerful tools."
>
> This guy certainly did miss maven archetypes. Asides from that, we
> actually could think about some code generation tools. For example:
>
> $> struts-gen.sh de.grobmeier.app.LoginAction
>
> Generated LoginAction.java
> Generated login.jsp
>
> This paragraph also tells me we should stick with the idea of pushing
> the Convention plugin.
>
> Later the author wrote:
>
> "Awful official documentation. User-written tutorials are slightly better."
>
> As already discussed today, I think this is not so wrong.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>


-- 
Cheers,
Paul

Reply via email to