You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2013/01/21 09:16:14 UTC
[jira] [Updated] (SYNCOPE-280) Update some checked exceptions to
runtime ones
[ https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Shakirin updated SYNCOPE-280:
------------------------------------
Fix Version/s: 1.1.0
> Update some checked exceptions to runtime ones
> ----------------------------------------------
>
> Key: SYNCOPE-280
> URL: https://issues.apache.org/jira/browse/SYNCOPE-280
> Project: Syncope
> Issue Type: Improvement
> Reporter: Andrei Shakirin
> Assignee: Andrei Shakirin
> Fix For: 1.1.0
>
>
> Accordingly Java Best Practices checked exceptions should be used only for conditions from which the caller can reasonably be expected to recover.
> Runtime exceptions should be used for preconditions violation and for programming errors.
> Candidates for checked exceptions are:
> - InvalidSearchConditionException
> - NotFoundException
> Candidates for runtime exceptions:
> - all Validation exceptions inherited from javax.validation.ValidationException
> - MissingConfKeyException
> - AccountPolicyException
> - PasswordPolicyException
> - PolicyEnforceException
> - IncompatiblePolicyException
> - UnauthorizedRoleException
> - PropagationException
> - ReportException
> - WorkflowException
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira