[
https://issues.apache.org/jira/browse/ARTEMIS-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851480#comment-17851480
]
Josh Byster commented on ARTEMIS-4780:
--------------------------------------
[~jbertram] Makes sense. Perhaps it could scan through MBean looking for
packages matching artemis? I don't think it's super far-fetched to say that the
people who will relocate their artemis dependencies will still have "artemis"
in the name, or at least can be one thing to try. Usually I'd assume they'd
just prefix the package with some shaded prefix.
> Artemis web console does not ever set 'artemisJmxDomain' in localStorage
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-4780
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4780
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.32.0
> Reporter: Josh Byster
> Priority: Minor
>
> We relocate our artemis packages as part of our shading process.
> I did set up:
>
> {code:java}
> aActiveMQServer.getConfiguration().setJMXDomain("com.abc.shaded.org.apache.activemq.artemis");
> {code}
> However the web console does not show up. I noticed in the code it's because
> we try to read in localStorage['artemisJmxDomain'] but never actually set it
> as far as I can tell. Thus we always default to org.apache.activemq.artemis.
> Everything works properly when setting localStorage['artemisJmxDomain'] =
> "com.abc.shaded.org.apache.activemq.artemis"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
