[ http://issues.apache.org/jira/browse/AXIS-2491?page=comments#action_12415281 ]
pmag10 commented on AXIS-2491: ------------------------------ Hi Bjorn, Sorry for the late answer due to vacation :-) You'll find below an example of the SOAP request related to our issue : <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <ns1:GDHeader soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"; soapenv:mustUnderstand="0" xmlns:ns1="http://server.sgw.gd.ctm.com";> <ns1:ResponseContext> <ns1:RequestID>ReqHeader123456</ns1:RequestID> <ns1:SystemID>MMS-GW1</ns1:SystemID> <ns1:Timestamp>2006-06-07T18:23:07.402+01:00</ns1:Timestamp> <ns1:Echo>WW05dWFtOTFjblJ2ZFhOc1pYTXlORzF2Ym1SbGN3PT0=</ns1:Echo> </ns1:ResponseContext> </ns1:GDHeader> </soapenv:Header> <soapenv:Body> <SvcConfirmRsp xmlns="http://server.sgw.gd.ctm.com";> <Message> <MsgID>30</MsgID> </Message> <Info> <Context/> </Info> </SvcConfirmRsp> <Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/";> <faultcode xmlns="">soapenv:Server</faultcode> <faultstring xmlns="">Context is inactive</faultstring> <faultactor xmlns="">SGW-GD</faultactor> <detail xmlns=""> <ns2:gdfaultdetails xmlns:ns2="http://server.sgw.gd.ctm.com";> <ns2:code>701</ns2:code> <ns2:type>2</ns2:type> </ns2:gdfaultdetails> </detail> </Fault> </soapenv:Body> </soapenv:Envelope> Thanks for help. > Fault element handling into SOAP Request > ---------------------------------------- > > Key: AXIS-2491 > URL: http://issues.apache.org/jira/browse/AXIS-2491 > Project: Apache Axis > Type: Bug > Versions: 1.2.1 > Environment: Solaris 8 > Reporter: pmag10 > > We've implemented a "asynchronous" SOAP/1.1interface based on Axis 1.2.1 in > the following way : > - Submitter [A] sends a SOAP request to [B] > - B acknowledges it and starts processing the incoming request > - Processing result is forwarded by [B] to [A] (so B becomes the client and > [A] the server) > - once the initial SOAP request as been acknowledged by [B], if the > business logic process fails, the error cause is returned to [A] using the > SOAP Fault element (architecture choice) -> it means that a Fault element is > introduced into a SOAP request > As far as we've seen, SOAP/1.1 specifications or additional 3w notes do not > specified that the element Fault is forbidden into SOAP request but just that > the Fault element is "mainly" used into SOAP response (which is really clear). > Based on that, we have 2 questions : > - [Q1] - Are we compliant with SOAP/1.1 specifications ? > - [Q2]- If yes, in this case why the Axis [A]client is not hable to process > properly the SOAP message sent by [B] : > - indeed, when server [A] receveives the incoming SOAP request > including a SOAP Fault element, no exception is raised (which is the expected > behavior) but the Fault element is raised by Axis to the application layer > set to null, which is to our mind a bug. > Regards, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
