You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2011/04/08 18:34:06 UTC

[jira] [Resolved] (DISCOVERY-11) Service.providers Enumeration does not catch and discard UnsatisfiedLinkErrors and ExceptionInInitializerErrors

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

Simone Tripodi resolved DISCOVERY-11.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.5
         Assignee: Simone Tripodi

Fixed according Joerg's suggestion, see Service r1090329

> 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
>            Assignee: Simone Tripodi
>             Fix For: 0.5
>
>
> 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