[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [REL-49]proposal for REL-49
Salient points are:
Example of a <service-config> usage inside the operation 'foorBar'.
<portType name="fooPortType">
<operation name="fooBar">
<wsrm:service-config xmlns:wsrm="some URI" wsdl:required="true">
<!-- Spec. version>
<wsrm:version>1.0</wsrm:version>
<!-- We can also have
some kind of capability parameters
<wsrm:batching-support>
{true|false}
</wsrm:batching-support>
<wsrm:piggyback-support>
{true|false}
</wsrm:piggyback-support>
-->
<wsrm:guaranteed-delivery>
<!-- List the reply patterns supported by this service.
Can have one or more such patterns -->
<wsrm:reply-pattern>
Callback <!—possible values are Response/Callback/Polling ->
</wsrm:reply-pattern>
</wsrm:guaranteed-delivery>
<wsrm:duplicate-elimination>
true
</wsrm:duplicate-elimination>
<wsrm:message-ordering>
true
</wsrm:message-oredering>
</wsrm:service-config>
<input message="fooMessageIn" />
<input message="fooMessageOut>
</operation>
</portType>
Client side config sample:
<wsrm:client-config xmlns:wsrm="some URI">
<!-- No. of retries to send for non ack. messages
and return interval -->
<wsrm:retry-config>
<wsrm:retry-count>5</wsrm:retry-count>
<wsrm:retry-interval>10</wsrm:retry-interval>
<!-- 10 secs
</wsrm:retry-config>
<!-- Can have only one such pattern. If
the pattern is 'Callback',
the reply-to attribute can also be used -->
<wsrm:reply-pattern wsrm:reply-to="SomeURIToSendAcksAndFaults">
Callback <!—possible values are Response/Callback/Polling ->
</wsrm:reply-pattern>
<wsrm:group-config>
<wsrm:group-expiry-time>dateTime</wsrm:group-expiry-time>
<wsrm:group-max-idle-duration>dateTime</wsrm:group-max-idle-duration>
</wsrm:group-config>
</wsrm:client-config>
-Sunil
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]