> In other words, in Stripes you'd have
>
> private User user;
>
> /* getters and setters */
>
> public Resolution save() {
> // do something with user
> }
>
> In Spring MVC you'd have
>
> public void save(User user) {
> // do something with user
> }
>
> The "do something"s in both Stripes action beans and Spring controllers are
> best left to injected helpers, daos, and so on, keeping the action/controller
> classes simple.
>
> So, in that respect, I'm not sure that using local variables leads to more
> complex procedural code, if you keep things simple in controllers.
The main drawback to the Stripes approach is that if you have multiple
handlers on a single action it becomes ambiguous which bean properties
are inputs to each action. When they are arguments to the handler
method it is super clear what applies where. I wouldn't mind
sometimes if Stripes supported either approach - why not just look for
any method that returns Resolution and then if there are parameters,
try to bind them, if you can? (yes, you probably need annotations to
tell you the name to bind on, but I can live with that)
Cheers,
Simon
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
