// apologizing for posting the same message on the user list as well

Hello All,

Is there implementation of JMX-WSDM adaptor in MUSE. I think Hideharu did
some developement in 2006 on this and added into MUSE. Can anybody point me
where it is in the code (in the directory structure of MUSE)?

I am copying Hideharu's email here just for developers so that you can
easily recall it. you can also find on this link
http://marc.info/?l=muse-dev&m=113885960919290&w=2


Please let me know where I can find this library or any hint on the
development of this JMX-WSDM adaptor.

Thank you in advance.

Best Regards,
Rahul

-----

> ----- Original Message -----
> From: "Hariharasudhan.D" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Friday, January 27, 2006 11:26 PM
> Subject: Re:WSDM-JMX adapter
>
>
>> Hi Hideharu Kato,
>>
>> I couldn't checkout the code from svn
>>
>> From: Hideharu Kato [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, January 26, 2006 7:55 PM
>> To: [email protected]
>> Subject: WSDM-JMX adapter
>>
>> Hi, everyone,
>>
>> I have been developing the WSDM-JMX adapter features. Now I committed
>> them
>> to muse.
>>
>> http://svn.apache.org/viewcvs.cgi/webservices/muse/trunk/wsdm-jmx/
>>
>> The WSDM-JMX library enables JMX MBeans to be accessed via WSDM
>> interface.
>> Currently it has some limits of the WSDM Resource - MBean mapping,
>> but can provide a kind of basic functionality as follows:
>>
>> - get MBean attribute values by using wsrf:GetRP
>> - start monitoring an MBean attribute by using wsn:Subscribe
>> - send JMX notification as wsn:Notify
>>
>> I would appreciate that if you would have a chance to use the library and
>> give some comments, questions and feedbacks to me.
>>
>> Regards,
>>
>> Hideharu Kato-- 
-- 
View this message in context: 
http://www.nabble.com/JMX-WSDM-adaptor-tp17632519p17632519.html
Sent from the Muse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to