Your plug-in is a very frequently requested feature, but it definitely looks a lot like what is called "action chaining", which is not considered a Struts best practice. You can search the mail archives for more information. As a quick summary, action chaining is considered a bad idea because it generally indicates that logic that should be in a separate business tier has been pushed up inappropriately to the presentation tier. If you are looking for a way to chain commands in the business tier you might want to investigate the Commons Chain package, which is currently in the jakarta commons sandbox.
I think the objection to chaining is more to do with the fact that it re-invokes the RequestProcessor chain than because of any specifics of how you organize your code.
At least, Ted is currently advocating (in another thread) that we support one formalized way of chaining exactly two actions; that is, to add support for an action registered to execute in the role of a "ViewController".
I haven't had much time to look closely at the Action Wrappers proposal, but it sounds like it may just be an alternative way of achieving the same goal, perhaps with more flexibility. That doesn't sound bad.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "We want beef in dessert if we can get it there."
-- Betty Hogan, Director of New Product Development, National Cattlemen's Beef Association
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
