[
https://issues.jboss.org/browse/REMJMX-43?page=com.atlassian.jira.plugin....
]
Darran Lofthouse updated REMJMX-43:
-----------------------------------
Fix Version/s: 1.0.4.CR1
(was: 1.1.0.Beta1)
The plan is to implement this by extending the URL supplied by the client.
This will involve an additional step at the start of negotiating the connection so version
2 of the protocol will be required.
Client side if this is a connection against a server that does not support the required
version of the protocol then an error needs to be reported so the client does not silently
connect to the wrong MBeanServer.
Add support for an MBeanServer / MBeanServerConnection locator
--------------------------------------------------------------
Key: REMJMX-43
URL:
https://issues.jboss.org/browse/REMJMX-43
Project: Remoting JMX
Issue Type: Task
Components: Connection
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.4.CR1
The idea of adding a 'locator' is so that we can add a query string to the
request URL and this can contain additional information to call out to a locator to find
either the referenced MBeanServer or MBeanServerConnection.
The Remoting JMX side of the implementation is just to add the locator API and to make
use of it including the addition of support for query string.
One place to consider using this is within AS7 where a connection will be made to the
master domain controller and the query string will identify a process to manage - the
locator will then either return the MBeanServer or MBeanServerConnection - the end result
will be that the master process becomes a proxy to the other processes providing a shared
entry point and shared connections to other processes to be managed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira