river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon IJskes (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (RIVER-382) Standardize Exception usage in River
Date Fri, 05 Oct 2012 08:16:47 GMT

     [ https://issues.apache.org/jira/browse/RIVER-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Simon IJskes closed RIVER-382.
------------------------------

    Resolution: Unresolved

No concensus could be reached. Please reopen and present your case at the river-dev mailinglist.
                
> 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

Mime
View raw message