-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 4 Dec 2005, Sylvain Wallez wrote:
Date: Sun, 04 Dec 2005 11:48:37 +0100
From: Sylvain Wallez <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: [RT][long] Cocoon 3.0: the necessary mutation
Gianugo Rabellino wrote:
Don't forget tools! In Cocoon 2.x it's basically impossible to
provide decent productivity tools because there are too many
components with contracts being too loose. If Cocoon 3 has to
happen, this is one of the points I will tend to commit myself to,
ensuring that every functionality can be easily managed, deployed
and monitored (JMX, anyone?) and that those mundane and boring tasks
that affect a Cocoon developer's life can be done using some fancy
web interface or an IDE.
JDK 1.5 has a JMX console and AFAIU Spring allows to easily JMX-ify
beans. So that may come for free.
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?
- --
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)
iD8DBQFDlGX1LNdJvZjjVZARAsKlAJ9nEDwqt5mxWYMINLmwE6TMSMMLJACff5iu
9tqmAaEx/0yOXb5HgBQOVhM=
=Dez6
-----END PGP SIGNATURE-----
