Matt Munz wrote:
Thank you matt. That is exactly what I am thinking.What's wrong with mbeanServer().registerMBean(mmb, name) ?
The first time you lookup an EJB or JMS connection, we we lazily force the client side to have an MBeanServer. Then we register only the mbeans required to service that object. For an EJB that may mean just a light weight client side container and a cache MBean. For JMS we would register a client side container and a reverse invoker.
I'm not talking about anything heavy weight. I still want this to be able to run on a cellphone. If the programmer decides that they want a heavier solution they can start an MBean server a startup with a sar deployer.
I guess I'm thinking that some clients will not want to get overly involved with the file system.
Like applets.
Agreed. All I am talking about is an MBean server. If someone wants more JBoss services on the client side they can do that, but it shouldn't be required.JMX on the client side and JBoss on the client side are two different things, right? AFAIK, MBeanServerFactory.createMBeanServer() doesn't require the service deployer. If it does, that's another thing...
-dain
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development