Hi Laurent, If you need to transform the soap11 fault into a soap12 fault before the transformation then you need to use a makefault mediator with soap12 and there you will have to copy the properties of the soap11 fault into soap12 fault using xpath expressions to retrieve information of the soap11 fault.
But I strongly believe that this is not the best solution. May I know the reason why you cannot change the transformation to cater the soap11 faults as well. Is this an xslt transformation? If so you could easily do this by adding a new template for the soap11 faults. If you can share the xslt I can provide the necessary changes to the transformation. Thanks, Ruwan On Thu, Jul 3, 2008 at 7:35 PM, Laurent CHARTIER < [EMAIL PROTECTED]> wrote: > Hi, > I have a simple question but I can't get a synapse.xml working. > > I have a sequence which sends a WS-request to an endpoint. Actually the > format is soap12. > If the response is a SOAPFault then the "onError" property points to > another > sequence which transform the soapFault. > > The fact is that this transformation can only be done from a SOAP 1.2 > soapFault. > > I have to invoque a SOAP 1.1 endpoint. No problem to change the format to > soap11 in the address endpoint in order to have a SOAP 1.1 request. > But then, if this endpoint returns a soapFault, it is a SOAP 1.1 fault and > the transformation can't work. > > What can I do before the transformation of a soapFault to be sure the > soapFault is a SOAP1.2 fault? And if not, how can I convert from SOAP 1.1 > to > SOAP 1.2? > > Thanks, > Laurent. > > > > Ce message est protégé par les règles relatives au secret des > correspondances. Il est donc établi à destination exclusive de son > destinataire. Celui-ci peut donc contenir des informations confidentielles. > La divulgation de ces informations est à ce titre rigoureusement interdite. > Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur > dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que > toute pièce jointe. > > This message is protected by the secrecy of correspondence rules. > Therefore, this message is intended solely for the attention of the > addressee. This message may contain privileged or confidential information, > as such the disclosure of these informations is strictly forbidden. If, by > mistake, you have received this message, please return this message to the > addressser whose e-mail address is written above and destroy this message > and all files attached. > > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
