The thing is that JMX is not protocol. There are JMX connectors using SOAP or RMI or other protocols. And ServiceMix does not really help in exposing a bean through JMX, but you could leverage spring for that: write a jaxws annotated POJO for example and configure a jmx wrapper in the xbean.xml in addition to exposing it over soap/http and any other protocols...
On 10/2/07, Raja Nagendra Kumar <[EMAIL PROTECTED]> wrote: > > Hi, > > As part of our business needs, we need to write a new custom JMX component > and deploy the same in ESB. The JMX Component takes a bynary data and does > store that data into a local file. > > In this regard, could any one point us to right example and tutorial, which > gives details of how to write a simple jmx component (which may have just > one method, on remote invocation it may just say hello) which could be > invoked remotely by JMX client, http client and/or webservice client (3 ways > of invoking the same). > > Any references to similar code in service mix code base or unit tests would > also be fine. > > Regards, > Raja Nagendra Kumar, > C.T.O > www.tejasoft.com > -- > View this message in context: > http://www.nabble.com/How-to-write-a-new-JMX-Component-and-depoy-the-same-ESB-tf4556110s12049.html#a13003162 > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
