[
https://issues.apache.org/jira/browse/DISCOVERY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017509#comment-13017509
]
Joerg Schaible commented on DISCOVERY-11:
-----------------------------------------
No, Errors should not be catched in general. Here it is enough to catch
additionally LinkageError that covers all the problems that arise from
dynamical class loading including the ones mentioned explicitly by Michael.
> 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
