OASIS ebXML Messaging Services TC

 View Only

Re: Fw: [ebxml-msg] Re: SOAP Fault location

  • 1.  Re: Fw: [ebxml-msg] Re: SOAP Fault location

    Posted 11-13-2001 08:20
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ebxml-msg message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


    Subject: Re: Fw: [ebxml-msg] Re: SOAP Fault location


    There is no reason why a SOAP Fault message cannot include the
    ebXML MessageHeader SOAP extension header(s) to identify the
    context of the fault. The SOAP Fault message is only a description of what is
    REQUIRED in a SOAP Fault, it is not limited to just an empty envelope
    with a SOAP-ENV:Fault element.

    Cheers,

    Chris

    iwasa wrote:
    009e01c16bf1$6ea45b80$d960a485@iwasalaptop">
    Arvola,

    I think this is an error handling issue. Please put this on the issue list.

    SOAP message/Fault does not have messageID/Reference message ID,
    so ebXML can't identify the message from SOAP Fault message.

    Thanks,

    Iwasa

    I received a question about SOAP Faults and ebXML Error from a developer.

    Q1. When receiver side MSH returns an error condition to sender side MSH,
    can the receiver side MSH send both ebXML Error and SOAP Fault using
    one HTTP response (or one separate HTTP request in asynchronous mode)
    at same time ?

    I guess the answer to the question is "No".


    Q2. The ebXML Message Service spec says:

    "When asynchronous mode of message exchange is being used, a
    HTTP response code in the range 2xx MUST be returned when the
    message is received successfully and any error conditions
    (including SOAP errors) must be returned via a separate HTTP
    Post." (on P65 in v1.05)

    However if answer to the Q1 above is "No", when sender side MSH
    received a SOAP Fault by a separate HTTP POST in asynchronous mode,
    how the sender side MSH know that which sen t messages's error is
    indicated by the SOAP Fault? SOAP Fault itself has not
    RefToMessageId element...


    Regards,

    --
    SHIMAMURA Masayoshi <shima.masa@jp.fujitsu.com>
    TEL:+81-45-476-4590(ext.7128-4241) FAX:+81-45-476-4726(ext.7128-6783)
    Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED


    ----------------------------------------------------------------
    To subscribe or unsubscribe from this elist use the subscription
    manager: <http://lists.oasis-open.org/ob/adm.pl>


    ----------------------------------------------------------------
    To subscribe or unsubscribe from this elist use the subscription
    manager: <http://lists.oasis-open.org/ob/adm.pl>



    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


    Powered by eList eXpress LLC