cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hamilton Verissimo de Oliveira (Engenharia - SPO)" <hamilton.olive...@agenciaclick.com.br>
Subject Re: [RT] On building on stone
Date Thu, 25 Mar 2004 16:58:09 GMT
-----Mensagem original-----
De: Thor Heinrichs-Wolpert [mailto:thor@lunartek.com]

> 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.


Mime
View raw message