[
https://issues.apache.org/jira/browse/RIVER-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479677#comment-13479677
]
Simon IJskes commented on RIVER-382:
------------------------------------
Refer to
http://mail-archives.apache.org/mod_mbox/river-dev/201210.mbox/%3C1350573637.8209.34.camel%40cameron%3E
for a detailed explanation.
> Standardize Exception usage in River
> ------------------------------------
>
> Key: RIVER-382
> URL: https://issues.apache.org/jira/browse/RIVER-382
> Project: River
> Issue Type: Wish
> Reporter: James Grahn
> Priority: Minor
>
> The public API of River currently throws many, many exceptions. I propose
> wrapping any Exceptions bubbling up to the public API to be wrapped in
> RiverException. Those few(?) River users who have special handlers to deal
> with problem conditions can peek into the cause to extract what information
> they need.
> From my observation, most libraries are either taking this route (ala JAXB)
> or wrapping everything in runtime exceptions (Spring, IIRC).
> (This suggestion was made based on experience with JavaSpace, but applies to
> the whole project.)
--
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
