cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: JMX integration (was: Re: [RT][long] Cocoon 3.0: the necessary mutation)
Date Mon, 05 Dec 2005 21:36:12 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 5 Dec 2005, Gianugo Rabellino wrote:

> Date: Mon, 5 Dec 2005 18:04:49 +0100
> From: Gianugo Rabellino <gianugo@gmail.com>
> Reply-To: dev@cocoon.apache.org
> To: dev@cocoon.apache.org
> Subject: Re: JMX integration (was: Re: [RT][long] Cocoon 3.0: the necessary
>     mutation)
> 
> On 12/5/05, Giacomo Pati <giacomo@apache.org> wrote:
>> While we are at it. I actually have the need for some JMX
>> instrumentation in Cocoon 2.1. But instead of just writing some MBean
>> wrappers for my components, I'd like to spent some more time on it for a
>> more general solution to it (monitoring component pool sizes come to my
>> mind quickly).
>>
>> Is there any interest do discuss this topic for a possible
>> implementation?
>
> Most definitely yes. However, be warned that retrofitting JMX to the
> current Cocoon architecture seemed like a big headache to me. Maybe
> going through Excalibur instrumentation (which I've never been able to
> see working) could do, otherwise expect pain. Lots of.

Could you elaborate a bit more? I'm interested about oppiions.

Ciao

>
> Ciao,
> --
> Gianugo Rabellino
> Pro-netics s.r.l. -  http://www.pro-netics.com
> Orixo, the XML business alliance: http://www.orixo.com
> (blogging at http://www.rabellino.it/blog/)
>
>

- -- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDlLLQLNdJvZjjVZARAl/4AKDvP5RbxyQhdi8it32jgqJmuKmTlwCgjPh5
jgepC3MGVAun3IKX5iwzGME=
=lC6K
-----END PGP SIGNATURE-----

Mime
View raw message