You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Rafael H. Schloming (JIRA)" <ji...@apache.org> on 2014/05/01 21:57:16 UTC
[jira] [Resolved] (PROTON-495) fix proton constructors to not be so
brittle
[ https://issues.apache.org/jira/browse/PROTON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming resolved PROTON-495.
----------------------------------------
Resolution: Fixed
Assignee: Rafael H. Schloming
> fix proton constructors to not be so brittle
> --------------------------------------------
>
> Key: PROTON-495
> URL: https://issues.apache.org/jira/browse/PROTON-495
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Reporter: Rafael H. Schloming
> Assignee: Rafael H. Schloming
>
> Currently it is ridiculously easy to get exceptions like the one below. Given that we are providing an API, not an SPI, this should never be able to happen.
> Caused by: java.lang.IllegalStateException: Can't find service loader for org.apache.qpid.proton.messenger.MessengerFactory for implementation type ANY
> at org.apache.qpid.proton.ProtonFactoryLoader.loadFactory(ProtonFactoryLoader.java:107)
> at org.apache.qpid.proton.ProtonFactoryLoader.loadFactory(ProtonFactoryLoader.java:84)
> at org.apache.qpid.proton.Proton.<clinit>(Proton.java:55)
> ... 84 more
> java.lang.ExceptionInInitializerError: java.lang.ExceptionInInitializerError
--
This message was sent by Atlassian JIRA
(v6.2#6252)