[wsf-c-dev] [jira] Created: (WSFC-128) Provide proper soap fault reasons when executing security samples

[Evanthika Amarasiri (JIRA)]

Provide proper soap fault reasons when executing security samples
-----------------------------------------------------------------

                 Key: WSFC-128
                 URL: http://www.wso2.org/jira/browse/WSFC-128
             Project: WSO2 WSF/C
          Issue Type: Bug
          Components: Apache Rampart/C (Security)
    Affects Versions: 1.1.0
         Environment: Windows XP, guththila, Apache2.2.4
            Reporter: Evanthika Amarasiri
         Assigned To: Manjula Peiris


When executing the rampart samples when there are faults in the policy and service xmls the given soap fault reasons are not very appropriate and does not given a clear meaning of what the error actually is.

Message 1 - "Undefined error returned by business logic implementation"
=========
You get the above error message when the following faults occurr
a) When the <sp:IncludeTimestamp/> tag is commented only on the client side
b) When an invalid policy (invalid xml) is given at the sever side
c) When the policy on the client side does not match with the policy on the server side

Message 2 - "NULL paramater was passed when a non NULL parameter was expected"
=========
Gives the above error when the below error occurs
a) When all of the "securityTokenReference" options are commented out on the server side

Message 3 - "Builder done with pulling. Cannot pull any more"
=========
Occurs when,
a) When the <sp:IncludeTimestamp/> tag is commented on server side

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira