synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-566) Content of Soap 1.1 faultcode not correctly transformed into Soap 1.2 faultcode
Date Sun, 09 Aug 2009 13:06:14 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741077#action_12741077
] 

Ruwan Linton commented on SYNAPSE-566:
--------------------------------------

This has been fixed on the trunk as well as the 1.3 branch and will be available with the
1.3 release, with this issue I also fixed an issue with cloning the faults. SOAPFault shouldn't
be treated as normal OMElements because they are extended from a certain API to provide the
fault functionality.

> Content of Soap 1.1 faultcode not correctly transformed into Soap 1.2 faultcode
> -------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-566
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-566
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Adriaan Wisse
>            Assignee: Ruwan Linton
>             Fix For: 1.3
>
>
> We are using something like the following synapse configuration to convert soap 1.2 messages
to soap 1.1 messages
> <proxy name="SynapseProxy" transports="http, https">
> 	<target>
> 		<endpoint name="Soap11Webservice">
>                         <address uri="http://localhost/MySoap11Webservice" format="soap11"
/>
>                 </endpoint>
> 	</target>
> </proxy>
> This is all working well except when we are receiving a Soap Fault from the 'MySoap11Webservice'
like this:
> <?xml version='1.0' encoding='utf-8'?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
>       <SOAP-ENV:Body>
>             <SOAP-ENV:Fault>
>                          <faultcode>SOAP-ENV:Server</faultcode>
>                          <faultstring>Something went wrong</faultstring>
>             </SOAP-ENV:Fault>
>       </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> Synapse transforms this message using the org.apache.synapse.core.axis2.SOAPUtils into
the following soap 1.2 message:
> <?xml version='1.0' encoding='utf-8'?>
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
>     <soapenv:Body>
>         <soapenv:Fault>
>             <soapenv:Code><soapenv:Value>SOAP-ENV:Server</soapenv:Value></soapenv:Code>
>             <soapenv:Reason><soapenv:Text xml:lang="en">Something went wrong</soapenv:Text></soapenv:Reason>
>         </soapenv:Fault>
>     </soapenv:Body>
> </soapenv:Envelope>
> There are 2 problems here:
> 1. In Soap 1.2 Server should be translated to Receiver (also see http://java.sun.com/javaee/5/docs/tutorial/doc/bnbhr.html
where in Table 19-1 SOAP 'Fault Code Values' the other correct fault codes are)
> 2. The namespace prefix SOAP-ENV where Server is prefixed with is not known and should
be soapenv.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message