Hi
Here are more details about the spec (I created a UML class
diagram but I could not send it therefore if you want to
see it please send me an email and I will send it to you):
- ConnectorServer: protocol independent Interface for a server
side connector. It has a reference to the MBeanServer and
delivers the necessary info from the server's registered beans
and invokes the desired operation on them. The attributes and
operations offered are defined how the beans are managed like
query for beans, get bean info about a bean, get/set attributes
on a given bean and invoke an operation on a given bean.
In addition it must provide a way to register the ConnectorServer
to listen for certain notifications.
- RMIConnectorServer: RMI protocol dependent Interface for the
server side. More or less this Interface just offer the dynamic
MBean interface over the RMI protocol. Therefore this interface
offer an invoke() method without an Object Name as first parameter
because it is its own method invoke() to be called. This method
(in its implementation) will then call the MBeanServer invoke()
method where the first parameter will be considered as ObjectName
to determine which beans invoke() method should be called. This
could also be the ConnectorServer implementation itself. Thus
the client can call RMI server side invoke() method with the
ConnectorServer's object name as first parameter and "queryMBeans"
as second parameter and you will get back a list of beans.
- RMIConnectorServerImpl: implements both Interfaces above. Because
RMI calls throw a RemoteException this implementation has to
handle them in a protocol independent manner (wrap or convert them
into a ConnectorException). It also implements the notification
transfer back to the client(s ??).
- ConnectorClient: looks nearly the same as ConnectorServer but has
additional attributes (about the protocol like it the protocol
is able to handle Notifications (HTTP is not)). It also defines a
way to register/deregister for a notification listening and to get
the notifications.
- RMIConnectorClient: like RMIConnectorServer but the other direction
- RMIConnectorClientImpl: like RMIConnectorServerImpl but the other
direction
- ConnectorFactory: it has to allow the client to look up for the
available protocols/connectors (on the server side) and if
necessary to download the client classes from the server. Maybe
the ConnectorFactory is also a MBean which provides you with the
information about the network (which servers are available and
with which connectors) and then let you add the server - connector
client bean you like.
What do you think ?
Have fun
"Mad" Andy
> -----Original Message-----
> From: Schaefer, Andreas [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 02, 2000 12:16 PM
> To: 'jBoss Developer'
> Subject: [jBoss-Dev] jBoss JMX Spec
>
>
> Hi Geeks
>
> I would like to give you the prototype for the JMX management
> within EJX but
> my
> computer crashed and I have to wait till the end of the week
> to access the
> programs
> again.
>
> But in the meantime I have a specification proposal for a JMX
> handling in
> jBoss:
>
> - A connector which is the actual JMXAdaptor. The client part
> is the Stup of
> the
> JMXAdaptor (at the moment for RMI protocol).
>
> - Creation of a client side server where the user can register all its
> remote JMX
> MBean Servers. Afterwards all the MBeans registered at the
> remote JMX MBean
> Servers are accessible at the client side as they would be registered
> locally.
>
> - Client can select a protocol to access the remote JMX MBean
> Server on the
> client
> side server and it will take the appropriate connector.
>
> - Client side server can connect to as many remote MBean
> Servers as needed
>
>
> Have fun
>
> Andy "Mad" Schaefer
> MCSE, Sun Certified Java Programmer and Developer (1.1)
>
>
