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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: RE: [ebxml-bp] Question on asynchronous business signals?


BPSS level of description currentlhy abstracts over whether a
RequestResponse Transaction is done over a pair of connections or one.

CPPA is the level at which this is handled. EbXML "architectural" view
has been that this property of delivery style is not part of business
semantics, but is instead a technical implementation detail.

Two information items there [CPPA] need to be consulted: 

1. An attribute called "syncReplyMode" on the element
MessageCharacteristics with type

<xsd:simpleType name="syncReplyModeType">
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="mshSignalsOnly"/>      [Means the RM Ack, for
example, returns synchronously. All else has its own channel.]
<xsd:enumeration value="responseOnly"/>        [ Signals have own
channel -- look for the signal action and find the channel]
<xsd:enumeration value="signalsAndResponse"/>  [ Means that the Response
delivery channel synchronously includes Signals]
<xsd:enumeration value="signalsOnly"/>         [ Means Signals return
synchronously]
<xsd:enumeration value="none"/>                [ Everything asynchronous
]
</xsd:restriction>
</xsd:simpleType>

This attribute is central to figuring out what happens.

2. The CanSend or CanReceive elements can specify which DeliveryChannel
that signals occur over. Not needed when syncReplyMode is
"signalsAndResponse" or "signalsOnly". [In signalsAndResponse mode,
there might only be a signal available to send, btw.]

If you need to followup, shift the query over to ebxml-cppa list and
there will be several people to help.


-----Original Message-----
From: James Wowchuk [mailto:james.wowchuk@vcs.com.au] 
Sent: Wednesday, May 12, 2004 5:15 AM
To: 'ebXML BP'
Subject: [ebxml-bp] Question on asynchronous business signals?


In reading through the BPSS1.10 spec I'm at a loss to understand how to
distinguish in the BPSS where a business signal is to be returned
synchronously or asynchronously.  Obviously the "timeToAcknowledgeXX"
attribute in the <BusinessTransaction> will indicate if the signal is to
be returned. But in the scenario where the "Acknowledgement" is returned
immediately (synchronously) and the Business Signal
"AcceptanceAcknowledgment" is returned later (asynchronously), does not
the responsibility for the delivery mode fall within BPSS?  

In the case of an synchronous Acknowledgement, where no payload
(Business Signal) is included, this has impact on the name of the
Service element of the ebXML Message.

Possibly the complementary child elements of the CanSend->CanReceive or
CanReceive->CanSend can be used to determine synchronicity?  Yet where
the activities are asynchronous, how is it determined which
corresponding CanReceive/CanSend element is used for the asynchronous
Acknowledgement or Business Signal?  Or is that a question for the CPPA
folks?

My apologies if this has been covered elsewhere but I find the archives
difficult to search.

Jim Wowchuk                       jim@vcs.com.au
Vanguard Computer Services P/L
 _--_|\                           Post:  PO Box 18
/      \                                 North Ryde NSW 1670
\_.--._/ <---Sydney NSW           Phone: +61 (2) 9888-9688
      v      Australia            Fax:   +61 (2) 9888-3056


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