Hi Steve and all,
What are the functionalities you would expect from the management interface.
I have currently implemeted the functionalities provided by the Axis2 admin page so that those tasks can be performed using APIs. Below are some functionalities I have implemented so far;
Getting list of serviceGroups, services, operations, modules and transports
Getting and editing parameters at all levels (e.g. service parameters, global parameters)
Getting engaged modules at various levels (e.g. global, service)
Engage modules globally
Engage modules to services
Engage modules to operations
And I am using Apache commons.modeler package for JMX. Therefore, clients can access the management interface using a MBeanServerConnection object and using methods like invoke and getAttribute with the method or attribute name as a parameter. Is this good enough?
And when using the WS interface, the client is just a web services client, using Axis2, .NET or any other technology.
What specific feathers should the management interface support to use it with SmartFrog?
Regards,
Chathura.
