[ http://wso2.org/jira/browse/WSAS-518?page=all ]
Afkham Azeez resolved WSAS-518.
-------------------------------
Resolution: Won't Fix
This is because security handlers are placed in the security phase and the
tracng handler is in the op phase which is after the sec phase. We cannot track
messages that cannot be dispatched, and those that do not reach the op phase
> Security faults are not captured by soap tracer
> -----------------------------------------------
>
> Key: WSAS-518
> URL: http://wso2.org/jira/browse/WSAS-518
> Project: WSO2 WSAS
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1-RC2
> Environment: winxp, jdk15
> Reporter: Charitha Kankanamge
> Assigned To: Afkham Azeez
>
> Security faults (Timestamp exceptions etc..) are not captured by soap tracer.
> We may need to have a mechanism to capture and record them through soap
> tracer.
> Steps to reproduce:
> ================
> 1. Assign a security scenario to version service
> 2. Enable soap tracing
> 3. Perform tryit on version service
> 4. Check trace messages
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
