Not sold on Stripes.
Written on September 13, 2006 – 12:00 am | by mpayne
The actions look pretty much like webwork which is good. However, it appears like a step backwords. On the surface you may be able to get your feet wet a little quicker. However, without the configuration in place actions are tied to their view output. 1:1 mapping!!
In stripes, Action methods return exactly where to go.
ex:
return new ForwardResolution("/productDetail.jsp");
(btw: Tapestry also suffers from this problem)
I don’t know about you, but I’ve frequently had apps where same action was exposed under directly urls and views and sometimes with a different interceptor stack(e.g. security turned off under /demo). If you have to create another action just to expose it somewhere else, that is more work than just having a config file.
I’ll take a little extra config for a world more of flexibility. Though I don’t have to though the process of learning WW, since I already know it.