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] [Closed] (DISCOVERY-11) Service.providers Enumeration does not catch and discard UnsatisfiedLinkErrors and ExceptionInInitializerErrors
Date Wed, 01 Jun 2011 20:43:48 GMT

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

Simone Tripodi closed DISCOVERY-11.
-----------------------------------


included in discovery-0.5 release

> 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

Mime
View raw message