[jira] Updated: (TAP5-1357) Add ServletException to signature of HttpServletRequestFilter#service
[ https://issues.apache.org/jira/browse/TAP5-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Gavrilov updated TAP5-1357: - Fix Version/s: 5.2.5 Add ServletException to signature of HttpServletRequestFilter#service - Key: TAP5-1357 URL: https://issues.apache.org/jira/browse/TAP5-1357 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2.4 Reporter: Alexander Gavrilov Fix For: 5.2.5 It's common practice to wrap some native javax.servlet.Filter implementations into HttpServletRequestFilter and contribute that adapter to HttpServletRequestHandler. Signatures of both Interfaces almost match, but HttpServletRequestFilter does not declare ServletException as possible catched exception in the signature. This means that it's required to wrap ServletExcpetion into some RuntimeException wrapper to rethrow it. As i c there is no propblem to add this kind of ecxeption without break of existig functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1357) Add ServletException to signature of HttpServletRequestFilter#service
[ https://issues.apache.org/jira/browse/TAP5-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thiago H. de Paula Figueiredo updated TAP5-1357: Fix Version/s: (was: 5.2.5) The fix version is only set when a fix is committed to SVN. Add ServletException to signature of HttpServletRequestFilter#service - Key: TAP5-1357 URL: https://issues.apache.org/jira/browse/TAP5-1357 Project: Tapestry 5 Issue Type: Improvement Components: tapestry-core Affects Versions: 5.2.4 Reporter: Alexander Gavrilov It's common practice to wrap some native javax.servlet.Filter implementations into HttpServletRequestFilter and contribute that adapter to HttpServletRequestHandler. Signatures of both Interfaces almost match, but HttpServletRequestFilter does not declare ServletException as possible catched exception in the signature. This means that it's required to wrap ServletExcpetion into some RuntimeException wrapper to rethrow it. As i c there is no propblem to add this kind of ecxeption without break of existig functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
