[jira] Created: (JCI-47) Swallowing Exceptions makes debugging difficult

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (JCI-47) Swallowing Exceptions makes debugging difficult

Gilles (Jira)
Swallowing Exceptions makes debugging difficult
-----------------------------------------------

                 Key: JCI-47
                 URL: https://issues.apache.org/jira/browse/JCI-47
             Project: Commons JCI
          Issue Type: Improvement
    Affects Versions: 1.0RC2
            Reporter: Niall Pemberton


I've noticed that JCI swallows exceptions in a number of places. For example both the read() and write() methods do this in FileResourceStore. I think I've also seen it in at least a couple of other places (I'll try to put together a full list).

Maybe there should be a JCI run time exception that they throw - anyway at a minimum I think the exceptions should at least be logged IMO

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (JCI-47) Swallowing Exceptions makes debugging difficult

Gilles (Jira)

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

Torsten Curdt updated JCI-47:
-----------------------------

    Component/s: core

> Swallowing Exceptions makes debugging difficult
> -----------------------------------------------
>
>                 Key: JCI-47
>                 URL: https://issues.apache.org/jira/browse/JCI-47
>             Project: Commons JCI
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.0RC2
>            Reporter: Niall Pemberton
>
> I've noticed that JCI swallows exceptions in a number of places. For example both the read() and write() methods do this in FileResourceStore. I think I've also seen it in at least a couple of other places (I'll try to put together a full list).
> Maybe there should be a JCI run time exception that they throw - anyway at a minimum I think the exceptions should at least be logged IMO

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]