Hi, On Wed, 15 Jan 2003 09:11, Jakob Praher wrote: > I think it can be quite interesting, when it comes to the micro kernel > design, since all invocations, as in the micro kernel design pattern, go > through the kernel, which is the MBeanServer.
In most cases I consider JMX great for coarser grained components. In the end JMX is just the naming/plumbing part of "application server". I think it is great from a management perspective and for starting up coarse grained components but I don't think it works for fine grained components. In coarse grain components the slight overhead causes no worrys. However you will notice that people who try to build more fine grained components ontop of JMX end up having to do so much of the plumbing to get things right. ie You will find most of these MBeanServers will have internal interceptor chains that can be configured. They will also have a lot of other MBeanServer specific knobs to twiddle. Then you have to create a system for lifecycle (init/start/stop/destroy), naming, dependencies and start adding in all sorts of other bulk. And even with this the systems still wont be as efficient or easy to develope as a small strongly typed system. > In that way you get hot deployment for free. > The only drawback is speed. (you can use proxies for the convenience) > > On the other hand you can extend your system at runtime, without > restarting the whole system. > But this only makes sense on a coase grained subsystem level. - I don't > think one should do it for every single component. agreed. Ages ago I started to rebuild an Avalon container so that all of the fine-grained stuff was done via the Avalon container and the coarse grain stuff by JMX. It was an interesting experiment and would have been a great way to go forward but it was too much work (too much got duplicated between two component systems). ATM I am working to extract out the commonality so that it becomes viable to have a MBeanServer be the "spine" and the rest Avalon containers. So the MBeanServer would essentially federate a bunch of location independent Avalon containers. It is an interesting thought experiment but I am not sure how practical it is ;) Anyways it is still a bit of a way to go. -- Cheers, Peter Donald *------------------------------------------------* | Trying is the first step to failure. | | So never try, Lisa - Homer Jay Simpson | *------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
