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=32954>. 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=32954 Summary: Wildcard support in exception handlers Product: Struts Version: 1.2.6 Beta Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Standard Actions AssignedTo: dev@struts.apache.org ReportedBy: [EMAIL PROTECTED] It seems to me that <exception> elements nested inside <action-mapping> element would benefit of wildcard action mapping as much as nested <forward> already do. In particular I would suggest to modify the ActionConfigMatcher.convertActionConfig method in order to treat ExceptionConfigs in much the same way as ForwardConfigs (code not compiled): ExceptionConfig[] exConfigs = orig.findExceptionConfigs(); ExceptionConfig exCfg = null; for (int x = 0; x < exConfigs.length; x++) { exCfg = new ExceptionConfig(); exCfg.setPath(convertParam(exConfigs[x].getPath(), vars)); // copy other meaningful properties here config.removeExceptionConfig(exConfigs[x]); // note that the previous line is missing in the current code, // but asimilar one is used to handle ForwardConfigs config.addExceptionConfig(exCfg); } Regards, Fabio. -- 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]
