Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of joebohn@gmail.com designates
 72.14.220.152 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=lGxuhmuPU3WrBPHEhTdWCXd1hBOeY9cR012yeffBDty1hkV8QqFnCRmjUgQRVD/EGm
         zaP9SmSzMMrS+WjJDjccLtINfkCsJuH4KJg/+RIQYeFBQaI/GuhuZKBRATvWN/a7evfQ
         8hfXvdMOK5fjfDc+hOIqbcvj7gWldttYSFLxI=
Message-ID: <4ADF8621.7070909@gmail.com>
Date: Wed, 21 Oct 2009 18:07:29 -0400
From: Joe Bohn <joebohn@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: aries-dev@incubator.apache.org
Subject: Re: [jira] Commented: (ARIES-29) Implement JMX Agent
References: <989189.1256159939390.JavaMail.jira@brutus>
In-Reply-To: <989189.1256159939390.JavaMail.jira@brutus>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Adam,

I just added you as an aries-developer so you should be able to assign 
the jira to yourself now.  You may need to log-out then back in to jira.

Joe


Adam Wojtuniak (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462#action_12768462 ] 
> 
> Adam Wojtuniak commented on ARIES-29:
> -------------------------------------
> 
> If someone can assign this task to me I can start working on it . thanks.
> 
>> Implement JMX Agent
>> -------------------
>>
>>                 Key: ARIES-29
>>                 URL: https://issues.apache.org/jira/browse/ARIES-29
>>             Project: Aries
>>          Issue Type: New Feature
>>          Components: JMX
>>    Affects Versions: 1.0
>>            Reporter: Adam Wojtuniak
>>             Fix For: 1.0
>>
>>
>> Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a Managed Beans (MBeans).
>> JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean, Configuration Admin MBean,
>> Provisioning Service MBean, User Admin MBean, Conditional Permission Admin MBean.
>> It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services.
>> For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be registered (on all available MBean servers) when is discovered.
>