[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Supporting Signals in BTAs
Team,
I've upgraded the model and added signals - and
used the two
additional fields we discussed adding.
<Signals>
<Signal name="ReceiptAck" nameID="ReceiptAck2.7" specificationLocation="none" specificationID="BPSS-2.7" specificationType="" signalPurpose="signal" signalType="success"/> <Signal name="AcceptanceAck"
nameID="AcceptanceAck2.8"
specificationLocation="none" specificationID="BPSS-2.8" specificationType="" signalPurpose="signal" signalType="success"/> <Signal name="DefaultContext"
nameID="DefaultContext2.6"
specificationLocation="none" specificationID="BPSS-2.6" specificationType="ebContext" signalPurpose="setContext" signalType="context"/> </Signals>
This all went very smoothly. Notice that the
signal is not being included in the
BinaryCollaboration details - as agreed - its an
implied interaction only -
but the signal
is being written out into the BusinessTransaction definition,
as a RespondingBusinessActivity -
<DocumentEnvelope
businessDocument="ReceiptAck" nameID="ReceiptAck-01" isPositiveResponse="false" /> Since its a signal - the message handling should
default to the CPA definition
for signal handling - so that all works
too.
I think this is complete and works all very nicely
- I have no issues here to report.
Are there any other questions? If not - I
believe we can sign-off on the signal
items and declare victory.
Thanks, DW |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]