Don't we already offer two hierarchies for this purpose?
AuthenticationException and AuthorizationException
Les Hazlewood wrote:
This issue:
https://issues.apache.org/jira/browse/SHIRO-120
raises a good point. We shouldn't be swallowing exceptions from
Realms anywhere. We should instead offer a nice Exception hierarchy
to allow end-users to react to problems.
The best exception hierarchy I've seen exemplifying this is Spring's
DataAccessException and subclasses.
Should we incorporate something similar? If so, any recommendations?
- Les
