[ https://issues.jboss.org/browse/RTGOV-160?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-160: ----------------------------- Description: Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component. Once switchyard exposes the interface type via the consumer/provider metadata, then the serviceType in the activity events should reflect the interface type of the binding, rather than the internal interface used by the implementing component. was: Currently activity events for bindings are ignored, on the basis that they are providing a protocol specific mapping onto the real service. However if monitoring a scope wider than the services within the ESB, then it will be necessary to have details recorded about the events associated with the bindings, to be able to correlate the activities across the distributed environments. This means that (for example) there will appear to be two OrderService calls - although one will be associated with the binding, and the other with the service implementation. They will have different interface types, and the events associated with the binding should be flagged as such, so that post processing can take this into account. As part of this work we also need to more strictly specify the serviceType in the RPC activity events based on the interface, as this is the public view of the service. However we also need to record information about the service implementation providing the service, which is the subject of a separate jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira