|Hi Rickard
not the kiddo, he is sleeping (little angel ;-)
|I delved a little bit in jBoss Server code and discovered that you use
|java.lang.reflect.Proxy to create dynamic Proxy classes for a given
|Interface.
yes
|Before this I always thought that it is impossible to create a Proxy class
|on the JMX client side to deal with the remote MBeans without dealing
|with JMX Connector etc.
|But know the problem is that JMX does not send Interfaces to the client
|but a JMX structure to reflect the MBeans on the server-side.
|
|NOW my question is how to create an Interface on the client-side to
|create from this Interface the Proxy class or is there a way to create a
|proxy without an Interface?
You need an interface for the Proxy. The proxy is typed vis-a-vis the
clients, that's the whole point.
|The problem with JMX is that only standard MBeans have to implement
|an Interface but for the other types there is no interface.
the other interface for Dynamic MBeans is one with "invoke" so it would map
to the proxy invocation...
but I am not sure I am seeing where you go with the "dynamic MBeans"...
|If this is doable I will change the JMX Connector on the client-side
|therefore
|that the client see the Proxy-Objects and deal with them instead of the
|MBeanServer interface. What do you think?
If you are proposing typed management of the server through java programming
I am hearing you.
Ok, it is not very clear, I just want to make sure I understand what you are
proposing.
All our management today is done with MBean interfaces declared in the
server. Imagine these are seen by the client, it is then possible to build
a proxy that takes the calls under that interface and serves a "invoke" to
an invocation handler that is basically a wrapper that can call the JMX
Connector you have done.
I was thinking about that the other day for 3 reasons
1- I believe we ****need*** a typed approach to the management of J2EE
2- the JMX connector exports the "invoke" which would map nicely to the
proxy stuff.
3- I need this for various reasons :)))
mostly what I would like to see in JBoss is that we name all "connectors"
with "JDBC instance myOracleDB" or something like that and what you get back
is the MBean interface for the static wrapper instrumentation of JDBC
connections (we don't do that in JBoss, so imagine just turning on and off
the loggind ;-). We could then bind this in JNDI and have tools come in and
get that Proxy, JUST LIKE WE GET A EJB TODAY, and perform management
functions on these. Do you see the pluggable tools?
Also the Proxy needs not work solely with the RMI connector you have done we
could use the http protocol in there to actually carry the call... uuuuuuuu
the scalability... uuuuuuuu snmp what?
<did I just come in my pants? oh my how embarassing />
we need this.
marc
|
|Have fun - Mad Andy / Better Pizza
|
|Senior Java Developer
|eBuilt Inc. (www.ebuilt.com)
|
|while( true ) { think(); write(); publish(); }
|
|
|
