[
https://issues.apache.org/jira/browse/QPID-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Gemmell updated QPID-1481:
---------------------------------
Attachment: QPID-1481_22nov2008.patch
I have created QPID-1481_22nov2008.patch to modify the jmxremote.sasl plugin
manifest, directing the plugin to use the jmxremote_optional.jar as its
classpath, exporting the packages offered within it. Additionally, the
org.apache.qpid.management.ui plugin is altered to stipulate that the
jmxremote.sasl plugin is only an optional dependancy, allowing it to start
without the jmxremote.sasl plugin being successfully resolved.
After applying this patch, if the user places the jmxremote_optional.jar in the
jmxremote.sasl plugin's folder
($QPIDMC_HOME/eclipse/plugins/jmxremote.sasl_1.0.1) it will be picked up and
other plugins can make use of it without the need to modify the classpath.
> jmxremote.sasl plugin doesnt export packages for other plugins to use
> ---------------------------------------------------------------------
>
> Key: QPID-1481
> URL: https://issues.apache.org/jira/browse/QPID-1481
> Project: Qpid
> Issue Type: Bug
> Components: Java Management : JMX Console
> Affects Versions: M4
> Reporter: Robert Gemmell
> Attachments: QPID-1481_22nov2008.patch
>
>
> The jmxremote.sasl plugin was created in order to allow the
> org.apache.qpid.management.ui plugin to import the jmxremote_optional.jar
> file for use in providing authenticated management console connections to the
> broke. As such is listed as a dependancy of the org.apache.qpid.management.ui
> plugin on which the management console is based. However, it does not export
> the packages for other plugins to use, and additionally is only required when
> there is a desire to use the authentication security.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.