You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Malinda Kaushalye Kapuruge (JIRA)" <ji...@apache.org> on 2007/09/11 11:06:32 UTC

[jira] Closed: (RAMPARTC-19) SOAP Fault not generated if an error occurs when running rampart samples

     [ https://issues.apache.org/jira/browse/RAMPARTC-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Malinda Kaushalye Kapuruge closed RAMPARTC-19.
----------------------------------------------


Fixed issue

> SOAP Fault not generated if an error occurs when running rampart samples
> ------------------------------------------------------------------------
>
>                 Key: RAMPARTC-19
>                 URL: https://issues.apache.org/jira/browse/RAMPARTC-19
>             Project: Rampart/C
>          Issue Type: Bug
>          Components: samples
>         Environment: Windows XP, Ubuntu 7.04
>            Reporter: Evanthika Amarasiri
>            Assignee: Malinda Kaushalye Kapuruge
>             Fix For: 1.0.0
>
>
> Below are the steps to reproduce the issue
> 1. I was trying out a sample with a policy.xml file which does not match with the services.xml and received an error when running the sample. 
> E.g.:- policy.xml
> *************************************************************
>                 <wsp:Policy>
>                     <sp:MustSupportRefKeyIdentifier/>
>                     <!--sp:MustSupportRefEmbeddedToken/-->
>                     <!--sp:MustSupportRefIssuerSerial/-->
>                 </wsp:Policy>
> *************************************************************
> services.xml
> *************************************************************
>                     <wsp:Policy>
>                         <!--sp:MustSupportRefKeyIdentifier/-->
>                         <!--sp:MustSupportRefEmbeddedToken/-->
>                         <!--sp:MustSupportRefIssuerSerial/-->
>                     </wsp:Policy>
> *************************************************************
> 2. When monitored it through TCPMon noticed that it does not generate a SOAP Fault but only returns the following.
> *****************************************************************************************************************
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
> <wsa:MessageID>8c070a10-2081-1dc1-3583-000c29e6e517</wsa:MessageID>
> <wsa:RelatesTo wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply">8bf2f8a4-2081-1dc1-3a28-000c29e6e517</wsa:RelatesTo>
> </soapenv:Header>
> <soapenv:Body>
> </soapenv:Body>
> </soapenv:Envelope>
> *****************************************************************************************************************
> 3. Therefore, when such errors occur, it is preferable that you return a SOAP Fault

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.