Hi Alex, This is the soap fault that gets written into outputVariable. Is this soap fault message wrong? <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> <soap:Body> <soap:Fault> <soap:Code> <soap:Value>soap:Receiver</soap:Value> </soap:Code> <soap:Reason> <soap:Text xml:lang="en">Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.</soap:Text> </soap:Reason> <detail> <errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/";>Group cannot be found.</errorstring> <errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/";>0x80131600</errorcode> </detail> </soap:Fault> </soap:Body> </soap:Envelope>
Thanks, Lee Alex Boisvert-3 wrote: > > On Wed, Sep 9, 2009 at 10:29 PM, LeeCK <[email protected]> wrote: > >> Will ODE checks the response soap message against the schema in WSDL >> before >> writing it into the outputVariable? >> > > No. > > >> I've trouble getting the outputVariable to comply with the defined schema >> in >> WSDL. The invoke seems to ignored the schema defined in WSDL and write >> whatever response it gets into the outputVariable (even soapFault!!). >> > > This is quite unusual and probably indicate a failure to respect the SOAP > protocol on the part of the target service. Axis2 should detect SOAP > faults > and ODE should either suspend the process (activity recovery) or go into > exception handling in the process. > > alex > > -- View this message in context: http://www.nabble.com/Invoke%27s-outputVariable-doesn%27t-comply-with-defined-schema-tp25377513p25392682.html Sent from the Apache Ode User mailing list archive at Nabble.com.
