[
https://issues.apache.org/jira/browse/SYNAPSE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618957#action_12618957
]
Saliya Ekanayake commented on SYNAPSE-393:
------------------------------------------
I tried to recreate your issue but was unsuccessful. I used a simple proxy
service in Synapse with a SOAP 1.1. endpoint. Then I sent a SOAP 1.2 message to
synapse which simply results in a SOAP fault (I intentionally sets a wrong
EPR). I tracked the SOAP messages using TCPMon and the SOAP fault seems to get
converted nicely. I even did a simple debug, yet it came out clean. See the
SOAP faults given below.
SOAP 1.1 fault returned by the back end server.
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Body>
<soapenv:Fault
xmlns:axis2ns3="http://schemas.xmlsoap.org/soap/envelope/";>
<faultcode>axis2ns3:Client</faultcode>
<faultstring>The service cannot be found for the endpoint reference
(EPR) http://localhost:8086/axis2/services/EechoService</faultstring>
<detail />
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
SOAP 1.2 fault returned by Synapse after converting the previous one
<?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>axis2ns3:Client</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en">The service cannot be found for the
endpoint reference (EPR)
http://localhost:8086/axis2/services/EechoService</soapenv:Text>
</soapenv:Reason>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Thanks,
Saliya
> Convertion not complete when using SOAPUtils.convertSOAP11toSOAP12()
> --------------------------------------------------------------------
>
> Key: SYNAPSE-393
> URL: https://issues.apache.org/jira/browse/SYNAPSE-393
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.1
> Environment: OS: Windows XP SP2
> Reporter: Laurent CHARTIER
>
> When using org.apache.synapse.core.axis2.SOAPUtils.convertSOAP11toSOAP12() to
> convert a SOAP 1.1 message containing a SOAPFault to a SOAP 1.2 message, the
> method only converts the Envelope, the Header and the Body elements.
> The Fault element is not converted ans its structure is not transformed into
> a SOAP 1.2 Fault structure.
> Before using the method:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <soapenv:Body>
> <soapenv:Fault>
> <faultcode>soapenv:Client</faultcode>
> <faultstring>Erreur relative au referentiel des conventions.
> [Fichier de convention]</faultstring>
> <faultactor>Referentiel des Conventions.</faultactor>
> <detail>Il n'y a pas de convention qui corresponde aux issuer,
> supplier et service</detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> After using the method:
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
> <soapenv:Body>
> <soapenv:Fault
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
> <faultcode>soapenv:Client</faultcode>
> <faultstring>Erreur relative au referentiel des conventions.
> [Fichier de convention]</faultstring>
> <faultactor>Referentiel des Conventions.</faultactor>
> <detail>Il n'y a pas de convention qui corresponde aux issuer,
> supplier et service</detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
> It should be:
> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Client</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text>Erreur relative au referentiel des conventions.
> [Fichier de convention]</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Role>Referentiel des Conventions.</soapenv:Role>
> <soapenv:Detail>Il n'y a pas de convention qui corresponde aux
> issuer, supplier et service</soapenv:Detail>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
