You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2014/08/18 13:52:19 UTC

[jira] [Updated] (POOL-269) Specialize useless throws Exception

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

Michael Osipov updated POOL-269:
--------------------------------

    Description: 
Too many methods say {{throws Exception}} in their signature. This is neither helpful nor good API design. You never know what the exception is and where it came from.

An exception translation pattern has to be applied to make code usable, e.g., like the Spring project does or Maven with {{BuildException}}.

Unfortunately, this ugly practive has prevailed in several Apache projects like Lucene.

  was:
Too many methods say {{throws Exception}} in their signature. This is neither helpful nor good API design. You never know what the exception is and where it came from.

An exception translation pattern has to be applied to make code usable.

Unfortunately, this ugly practive has prevailed in several Apache projects like Lucene.


> Specialize useless throws Exception
> -----------------------------------
>
>                 Key: POOL-269
>                 URL: https://issues.apache.org/jira/browse/POOL-269
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Michael Osipov
>
> Too many methods say {{throws Exception}} in their signature. This is neither helpful nor good API design. You never know what the exception is and where it came from.
> An exception translation pattern has to be applied to make code usable, e.g., like the Spring project does or Maven with {{BuildException}}.
> Unfortunately, this ugly practive has prevailed in several Apache projects like Lucene.



--
This message was sent by Atlassian JIRA
(v6.2#6252)