[
https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19463:
-------------------------------------
So I've looked into this a bit, and I'm not sure what a good solution here is.
I could modify the IConnectionWrapper interface, to change public boolean canControl();
to public IStatus canControl(), but this would be an API change on an interface that
hasn't had a method added since 2012, with previous changes back in 2008.
Alternately, we could add a new interface with one method in it, but, that always seems a
bit drastic, and if this course were taken every time we needed an API change, we'd
have lots more single-method interfaces.
The first option could break other extenders of ours, but we're not actually aware of
any such extenders, so maybe we just don't care ;) I'll work on a patch to the
interface, because something about making a new interface for one method seems wrong to
me.
Cannot connect to remote server without runtime 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.Beta2
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)