Hi Chris, There was no requirement to expose a SOAP/REST API in the load balancer. Therefore there is no WSDL/WADL added.
BTW if your requirement is to examine the behaviour of TopologyEventProcessorChain it shouldn't be that difficult. Basically each processor corresponds to its event, if it didn't find the required event it will pass the call to the next processor. Once it finds the matching event it will build the Topology in Topology Manager and fire the matching event listener. Thanks Imesh On Tue, Dec 3, 2013 at 3:31 AM, chris snow <[email protected]> wrote: > In the case of the LB MessageProcessorChain, the following processors have > been added to the list: > > org.apache.stratos.messaging.message.processor.topology.ServiceCreatedEventProcessor > org.apache.stratos.messaging.message.processor.topology.ServiceRemovedEventProcessor > org.apache.stratos.messaging.message.processor.topology.ClusterCreatedEventProcessor > org.apache.stratos.messaging.message.processor.topology.ClusterRemovedEventProcessor > org.apache.stratos.messaging.message.processor.topology.InstanceSpawnedEventProcessor > org.apache.stratos.messaging.message.processor.topology.MemberStartedEventProcessor > org.apache.stratos.messaging.message.processor.topology.MemberActivatedEventProcessor > org.apache.stratos.messaging.message.processor.topology.MemberSuspendedEventProcessor > org.apache.stratos.messaging.message.processor.topology.MemberTerminatedEventProcessor > org.apache.stratos.messaging.message.processor.topology.CompleteTopologyEventIgnoreProcessor > > In a component that exposes a SOAP/REST API, I would look at the WSDL/WADL > to examine the API. As a WSDL/WADL aren't available for the LB component, > how can I examine the API without having to run the code and inspect the > MessageProcessorChain? > > Many thanks, > > Chris >
