Hi, I'm not a committer either, but I've been lurking on this list a bit and have learned a thing or two.
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. If you still think your plug-in is worthwhile after reading why people dislike Struts chaining, SourceForge could be a good place to get started. Matt ----- Original Message ----- From: "john sessler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 01, 2003 3:35 PM Subject: Action Wrappers. 2nd Request for Comments & Code Contribution > Hello All, > > I've developed code that I would like to submit for comment and > consideration for inclusion in the Struts code base whenever it becomes > ready for prime time. Following is a very brief description of the purpose > of the code. Complete information, code and API can be found here: > https://www.sistemas-jasper.com/indexStrutsActionWrappers.htm. > > Action wrappers are Struts actions that invoke other actions. The design > goal of action wrappers was to sift common functionality from actions so > that it can be reused. Action wrappers are meant to be plug and play > components. They are useful because they allow the designer to apply common > functionality to application specific actions. They are rather like > decorators because they can be applied to and and removed from their wrapped > actions without modification of the wrapped action. Action wrappers are > configured in the Struts configuration file. > > The idea for action wrappers originated from the need to protect JSP views > from being duplicated by the user simply by cutting and pasting the URL in a > new browser window address box. A problem very closely related to this one > which influenced the development of action wrappers is the problem of > insuring that an action is executed exactly one time even though the link or > form which leads to the action remains available to the user. > > The code works without modification to existing Struts code (1.1). However, > it uses a somewhat uncertain mechanism to accomplish action invocation. > Please read the API docs for class ActionProcessor for a description of the > mechanism and for possible solutions. > > I have never contributed code to an open source project before so I'd like > some guidance on how to go forward. > Thank you, > John A. Sessler > > > > > --------------------------------- > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
