[ https://issues.jboss.org/browse/JBIDE-19463?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19463: --------------------------------------- [~rob.stryker], hmm, ok. That's definitely good to know. But I have a couple of questions: 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. 2. If 1. is not doable, how can we make users aware of this? It can be pretty confusing - you create a server, start it, then see it in the JMX Navigator view, but you double-click it and nothing happens. So I have a couple of ideas: a) We could display an error when a user wants to connect in this situation where we don't support it. But it could be thought of as ugly - we simply don't support it, so why enable it and then show an error. b) We could add a note to the wizard where you create the Server Adapter. Currently we have this: "The selected profile does not require a runtime." (And below is a checkbox for creating a runtime.) So we could add: Note that you won't be able to make a JMX connection without a runtime. Or something like that. c) We do nothing :) If 1. is not doable (also, maybe not worth the time - JMX is not a big priority), then I would probably vote for 2.b). What do you think? -- This message was sent by Atlassian JIRA (v6.3.15#6346)