You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/12/27 21:23:58 UTC
[jira] [Updated] (QPID-7598) Data/Classpath URL Stream Handlers
assume the Broker is loaded by the JVM's system classloader
[ https://issues.apache.org/jira/browse/QPID-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7598:
-----------------------------
Description:
The Java Broker implements two URL Stream Handlers:{{data:}} and {{classpath:}}. It registers these with the JVM using the {{java.protocol.handler.pkgs}} system property. Unfortunately, this technique only works if the Broker's JARs are loaded by the JVM's System classloader. If the Broker is loaded by a child classloader (as might be the case if the Broker is embedded within a container, a maven plugin or testing framework) this technique fails.
There seem to be a few (ugly) workaround for this problem documented on-line, but I have not evaluated merits.
was:
The Java Broker implements two URL Stream Handlers:{{data:}} and {{classpath:}}. It registers these with the JVM using the {{java.protocol.handler.pkgs}} system property. Unfortunately, this technique only works if the Broker's JARs are loaded by the JVM's System classloader. If the Broker is loaded by a child classloader (as might be the case if the Broker is embedded within a container, a maven plugin or testing framework) this technique fails.
There seem to be a few (ugly) workaround for this problem documented on-line, but I have an evaluated merits.
> Data/Classpath URL Stream Handlers assume the Broker is loaded by the JVM's system classloader
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-7598
> URL: https://issues.apache.org/jira/browse/QPID-7598
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: Future
>
>
> The Java Broker implements two URL Stream Handlers:{{data:}} and {{classpath:}}. It registers these with the JVM using the {{java.protocol.handler.pkgs}} system property. Unfortunately, this technique only works if the Broker's JARs are loaded by the JVM's System classloader. If the Broker is loaded by a child classloader (as might be the case if the Broker is embedded within a container, a maven plugin or testing framework) this technique fails.
> There seem to be a few (ugly) workaround for this problem documented on-line, but I have not evaluated merits.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org