-----Mensagem original----- De: Thor Heinrichs-Wolpert [mailto:[EMAIL PROTECTED]
> So I think JMX can be a bolt on, or an underpinning depending on how > you use it. I'd be surprised if it didn't meet the core of what you > described blocks needed. If a block has a consistent API (Interface) > then any block that supports that API could be loaded/unloaded and > messaged to from other components using the JMX services and usage > guidelines. JMX really helps to develop a extremme loosely-coupled application. For JBoss its was a necessity, for Cocoon I don't know. And my personal feeling is that it can increase complexity.
