commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISCOVERY-11) Service.providers Enumeration does not catch and discard UnsatisfiedLinkErrors and ExceptionInInitializerErrors
Date Fri, 08 Apr 2011 11:24:05 GMT

    [ https://issues.apache.org/jira/browse/DISCOVERY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017404#comment-13017404
] 

Simone Tripodi commented on DISCOVERY-11:
-----------------------------------------

wouldn't be better letting users know that there are problem on loading their classes, instead
of simply swallowing exceptions and ignoring the class loading?
I'm worried that the proposed solution could drive crazy someone...

> Service.providers Enumeration does not catch and discard UnsatisfiedLinkErrors and ExceptionInInitializerErrors
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DISCOVERY-11
>                 URL: https://issues.apache.org/jira/browse/DISCOVERY-11
>             Project: Commons Discovery
>          Issue Type: Bug
>    Affects Versions: 0.4
>         Environment: Windows, Sun JDK 1.5.0.10
>            Reporter: Michael Rudolf
>
> The enumeration created by Service.providers does not catch UnsatisfiedLinkErrors and
ExceptionInInitializerErrors. The former can arise, if a class contains a call to System.loadLibrary(String)
in its static initializer, while the latter will be thrown, when a runtime exception is thrown
from the static initializer. Service.providers should catch and ignore these and it should
simply discard the class provoking the error as not available. As of version 0.4, Commons
Discovery just forwards these errors.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message