OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: Re: Ack Message Payload??

my response message (identified with "MessageType=Acknowledgement") contains
the current stock price in the ebXML message payload (like an RPC).

Is this an attempt to merge MS ACK with "Normal" Payload? Or, is it a
Business ACK with a payload?

If first, then the same effect could be achieved if the MessageType was
"Normal" instead of "Acknowledgement".

If second, I don't like it. It ties the meaning of MessageType to the
existence of the Payload itself. This overloads the MS, which would need to
deal with different kinds of ACKs. I can see that MS can "Notify" "Business
Layer" about the MS ACK, but I cannot think of any other kind of ACK
(whatever it might be) that the MS would need to deal with.

Another characteristic of this "Usage" is that both flavors might lead to a
situation when one would need to "ACK an ACK".

I really support the view =>

Let me see if I can make this clearer. A Business ACK is NOT the same as a
MS-level ACK. A Business ACK would NOT use a MessageType="Acknowledgment"
because that is reserved for MS use.

A Business ACK is of MessageType="Normal" and has an appropriate payload (or
not as the case may be,
but it is NOT clear at all how an empty payload is supposed to be
interpreted by the receiving business service/application!).

Maybe famous "ServiceInterface/Action" combo can do the trick with Business
ACK and empty payload?


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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC