DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33202>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33202 Summary: DispatchChainAction needs review Product: Struts Version: Unknown Platform: Macintosh OS/Version: Mac OS X 10.0 Status: NEW Severity: enhancement Priority: P3 Component: Controller AssignedTo: dev@struts.apache.org ReportedBy: [EMAIL PROTECTED] As it is currently written, the DispatchChainAction is not much use because there is no way to specify in which catalog the command should be looked up. (It was written before the catalog model was applied to commons-chain.) Furthermore, members of the community have raised the real concern that it is risky to accept arbitrary URL parameters and use them to execute code without some way of enumerating which values are permitted. It should be pretty straightforward to make use of the new ActionConfig property map to specify any number of config values, including specifying a single literal catalog name or indicating a second parameter which can be used to find the catalog name, and also specifying enumerations of any valid values which might be submitted by request parameter. Also, note that there is an unreleased feature currently in the commons-chain CVS which allows you to use a single string to specify a catalog and a command (separated by a ":" character). The release of this code might provide an alternate way to bring this action class back into full usefulness. Since I don't plan to use the DispatchChainAction, this is a low priority for me, but I thought some of the issues should be documented, since I was going through them in a private email. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
