The only think I don't like with this solution is that the JSP writer has to know the existence of the "command" attribute into request. Moreover if the Action writer forgot to call the "setup" method the request attribute will not set.
[Jeff Beal]
You can use a custom RequestProcessor instead of a common Action method [...] Another trick is to write a base Action class with a final execute [...]
Good, even if I prefer the first or your two option: the custom RequestProcessor solves the problem without forcing new rules and without forcing all my actions to derive from my base action.
As I told in a previous email, I prefer solutions that don't force new rules into team. So, the custom RequestProcessor ensure a new feature into my application with no restricions, as well as, if you use Velocity, you just need *one* programmer extends the StrutsLinkTool and *all* the JSP/VM writers just know, as natural it is, they have an extended $link object into VM pages.
As I already told: no rules, just features!
Gp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
