Here is a draft based on Sacha Schlegel’s analysis of
the problem of per Action configuration of delivery channels for mshSignals.
The proposed element name, subject to change, is
MshDeliveryChannel.
Some questions about the content:
1. The packaging will not normally be the same as the
packaging for the Action. It will normally just be a simple SOAP message or a
SWA message perhaps. So an optional packageRef attribute is available to refer
to a Package element for the Msh signal.
2. The channelRef refers to a DeliveryChannel element with
both a reference to transport details and docExchange details. It is also
possible to directly refer to these items. Normally the Transport element will
be relevant, but the DocExchange can describe security aspects of the Msh
signal data exchange.
<xsd:element name="MshDeliveryChannel">
xsd:annotation>
<xsd:documentation>
If
the MshDeliveryChannel is not present, the defaultMSHChannel will be used.
If
the MshDeliveryChannel is present but the syncReplyMode of the delivery channel
referenced in "ChannelId" indicates synchronous transport the element
will be neglected.
If
the MshDeliveryChannel is present, and syncReplyMode indicates asynchronous
transport and there is an OverrideMSHChannelId, then MshDeliveryChannel value
has precedence.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute
name="channelRef" type="xsd:IDREF"/>
<xsd:attribute
name="packageRef" type="xsd:IDREF"
use="optional"/>
</xsd:complexType>
</xsd:element>
The element is found in the context, and can occur zero or
one times.
Should this instead be zero or unbounded times? (for CPP
usage for example.)
<xsd:complexType name="ActionBindingType">
<xsd:complexContent>
<xsd:restriction
base="tns:ActionBindingBaseType">
<xsd:sequence>
<xsd:element
ref="tns:BusinessTransactionCharacteristics"/>
<xsd:element
ref="tns:ActionContextHead" minOccurs="0"/>
<xsd:element
ref="tns:ChannelId" maxOccurs="unbounded"/>
<xsd:element
ref="tns:MshDeliveryChannel" minOccurs="0"/>
<xsd:any
namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute
name="id" type="xsd:ID" use="required"/>
<xsd:attribute
name="action" type="tns:non-empty-string"
use="required"/>
<xsd:attribute
name="packageId" type="xsd:IDREF"
use="required"/>
<xsd:attribute
ref="xlink:href" use="optional"/>
<xsd:attribute
ref="xlink:type" fixed="simple"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
I will be sending the entire draft of the 2.1 schema later
in the week when I resolve which of the tools I am using is correct (one says
valid, the other complains about an improper type restriction… Also I am
still working on identifying which sections need to be updated.)