[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
1. Could it not work the same way as connection via management api
when we have the client jars in the tooling itself? Because we do support this kind of
connection to a remote server even without a local runtime.
We do not bundle the jmx client jars. To do so would be a bit of a pain. We'd most
likely need to add new API and then also add new jars for each app server. For JMX we
tend to load the client-all jar onto the classpath, and bundling that would be... pretty
heavy.
Cannot connect to remote server in JMX Navigator
------------------------------------------------
Key: JBIDE-19463
URL:
https://issues.jboss.org/browse/JBIDE-19463
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.2.3.CR1, 4.3.0.Alpha1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta1
When you start a remote EAP 6.3 server with management enabled and set up and then want
to connect in JMX Navigator, it does not work - double clicking the connection will not do
anything and when you right-click, there is no Connect item.
For local servers this works fine - there is a Connect item when you right-click the
server in JMX Navigator.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)