joerghoh commented on pull request #6: URL: https://github.com/apache/sling-org-apache-sling-servlets-post/pull/6#issuecomment-733805913
Indeed, your approach would solve my problem as well; but I deem it more complex (or feature-rich) than it could be. For example your approach introduces a new extension point for mapping exceptions to status codes. Which is totally fine if this is actually needed, but I can only see my feature request which would make use of it right now. And my patch is much smaller to achieve more or less the same. I am absolutely in favor of your approach if more extensability is required, or if we need more granularity or when it comes to the various sources and wrapped exceptions of the PersistenceException. But right now it seems to solve a problem I don't need to be solved. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
