Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of seumas.soltysik@iona.com
 designates 65.223.216.181 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Managing (JMX) Configuration/Policy Beans
Date: Tue, 30 Jan 2007 18:10:52 -0500
Message-ID: <05F5FDC16A447442B12B21A432878AC505186E@amer-ems1.IONAGLOBAL.COM>
Thread-Topic: Managing (JMX) Configuration/Policy Beans
Thread-Index: AcdBc1nOx0i5zdP5RcO7ZW5YblRMJQDUN87g
From: "Soltysik, Seumas" <Seumas.Soltysik@iona.com>
To: <cxf-dev@incubator.apache.org>

One problem I see with depending on Spring to specify the JMX accessible =
interface is that I don't believe that Spring is always used to =
instantiate these policy/config objects. There are cases in the CXF code =
where Spring is not used to create new instances.

-----Original Message-----
From: Dan Diephouse [mailto:dan@envoisolutions.com]
Sent: Friday, January 26, 2007 12:56 PM
To: cxf-dev@incubator.apache.org
Subject: Re: Managing (JMX) Configuration/Policy Beans


Is this information we really want to keep in our schemas? Spring =
provides
an approach where you can control the MBean interface through the
MBeanInfoAssembler
interface. There are multiple implementations including one where we can
just specify what methods should be exposed as attributes in the =
spring.xml:

http://static.springframework.org/spring/docs/2.0.x/reference/jmx.html
http://static.springframework.org/spring/docs/2.0.x/reference/jmx.html#jm=
x-interface

- Dan

On 1/26/07, Soltysik, Seumas <Seumas.Soltysik@iona.com> wrote:
>
> It seems like it would be a good idea to be able to modify certain =
runtime
> attributes associated with the config/policy Spring Beans via JMX. =
Since
> only certain attributes make sense to modify at runtime, only these =
certain
> attributes should be exposed via an MBean. Could we integrate the
> information regarding which attributes should be exposed by annotating =
the
> existing schemas for the policies and then modifying the JAXB code =
generator
> to add JMX annotations to the appropriate getter/setter methods? This =
way we
> can ensure that only certain appropriate values can be changed via =
JMX.
>
>


--=20
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog