On Sun, Feb 6, 2011 at 8:37 AM, Afkham Azeez <az...@wso2.com> 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. Even for the incoming messages, SOAP tracer doesn't show the encrypted message as it sits after the Rampart handler. So we should set the tracer as the first handler in the inflow and last handler in the outflow. Thanks, ~Isuru > > 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: az...@wso2.com 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 > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
