Action item

Heylas,

Our current information on fault propagation rulesets looks like this:

<div2 id="fault-rules">
<head>Fault Propagation Rules</head>

<p>WSDL patterns specify their fault propagation model using standard
rulesets to indicate where faults may occur.  The most common patterns
for fault propagation are defined here, and referenced by patterns later
in
the document.</p>

<p>Generation of a fault, regardless of ruleset, terminates the
exchange.</p>

PROPOSED:

Add a paragraph between the two existing paragraphs, as follows:

<p>WSDL patterns specify propagation of faults, not their generation. 
Nodes which generate a fault MUST attempt to propagate the faults in
accordance with the governing ruleset, but it is understood that any
delivery of a network message is best effort, not guaranteed.  The
rulesets establish the direction of the fault message and the fault
recipient, they do not provide reliability or other delivery guarantees.
 When a fault is generated, the generating node MUST attempt to
propagate the fault, and MUST do so in the direction and to to the
recipient specified by the ruleset.</p>

Add a final paragraph to the section, as follows:

<p>Bindings, features, or extension specifications may override the
semantics of a fault propagation ruleset, but this practice is strongly
discouraged.</p>

Amy!
-- 
Amelia A. Lewis
Senior Architect
TIBCO/Extensibility, Inc.
alewis@tibco.com

Received on Thursday, 18 November 2004 18:22:19 UTC