Better support for SOA/SOAP tracing would be very useful.
We share that this feature (new SOAP Message body: request and response traces) have been included in Bizagi 9.1.9 version (released on May 2012).
Within these new traces, the SOAP body sent and receive is printed on separate files.
Authentication (and SOAP header) information is not included, as this could represent "sensitive information".
Thank you for your valuable feedback.
Could you please provide us further detail about the kind of trace messages and information you would expect to find?
The ability to see the result of serialization and deserialization of messages would be handy, items like time outs, authentication challenges and responses, events etc would also be helpful.
Comments have been locked on this page!