On Sun, Feb 6, 2011 at 8:37 AM, Afkham Azeez <[email protected]> wrote: > For the SOAP Tracer handler to capture all SOAP headers, it should be > the last handler in the out flow & out fault flow. However, the last > phase in these flows is Security, and the Rampart out handler has been > set as the phase last handler. So, there is no way for us to trace > security headers since these headers get added after the message is > traced. During demos, and troubleshooting sessions, the SOAP tracer is > a very useful tool. To overcome this, I think we should add a Trace > phase after the Security phase, and the Trace handler should be set as > both phase first and phase last. >
+1. To put the Tracer as the last handler better thing is to put a new phase. your point is correct. some times we want to see the security headers. But on the other hand some times we need to see the decrypted message. If you need to debug an data binding exception. so what about put an options to select where we want to log the message? thanks, Amila. > > Is there a better way of doing this? > > > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > > Member; Apache Software Foundation; http://www.apache.org/ > email: [email protected] cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > Lean . Enterprise . Middleware > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
