[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: AW: [ws-rx-implement] WS-RM/RX question...
3.2.:
To ensure that the Sequence ends with a known final state both the
RM
Source and RM Destination may
choose to 'close' the Sequence before terminating it.
4.2.:
This fault is sent by either the RM
Source or the RM Destination to indicate that it has either encountered
an
unrecoverable condition, or has detected a violation of the protocol and as a
consequence, has chosen
to terminate the sequence. The endpoint that
generates this fault should make every reasonable effort to
notify the
corresponding endpoint of this decision.
What are
the arguments to make only such a soft statement in 3.2.
Why do we really
need 4.2. and cannot always use close instead of terminate.
Do you have
examples when a closing is not possible but only a
termination?
From the
very first time I start thinking about WS-RM spec I worried about the
statement in 4.2. but maybe
this was because I always thought that a
terminated sequence must somehow be continued using a
new subsequent
sequenceID (think about offering the real application a stable serialization
context using
a sequence of underlying WS-RM sequences which are related. But
there is no relation between WS-RM
sequences and so this issue cannot be
solved on WS-RM level. So in case of a termination or closing, the
in-order
processing is interrupted and can only be handled using a protocol on a higher
level or by application
(e.g. a rollback work).
Do you
think it would be a good proposal to define subsequent WS-RM sequences on WS-RM
level
so that one can continue a sequence (by using a subsequent sequence)
after termination or closing (else only
a kind of rollback is possible, isn't
it?)? Or is this proposal out of scope of
WS-RM in your opinion? (Background:
how to offer the real application a stable serialization context
hiding
sequence terminations and sequence closing by just creating a
subsequent WS-RM sequence for a given
closed/terminated WS-RM
sequence?)
Von: Doug Davis [mailto:dug@us.ibm.com]
Gesendet: Mittwoch, 1. März 2006 14:15
An: Paul Fremantle
Cc: Rossmanith, Stefan; ws-rx-implement@lists.oasis-open.org
Betreff: Re: [ws-rx-implement] WS-RM/RX question...
Also, MaxMessageNumber has been removed from the spec.
-Doug
Paul Fremantle <paul@wso2.com> 03/01/2006 06:52 AM
To"Rossmanith, Stefan" <stefan.rossmanith@sap.com> ccDoug Davis/Raleigh/IBM@IBMUS, ws-rx-implement@lists.oasis-open.org SubjectRe: [ws-rx-implement] WS-RM/RX question...
Stefan
This is the usage for the CloseSequence, which still allows the RMS to
find out the final state of the sequence. So good behaviour would be for
the RMD to close the sequence not terminate it.
Paul
Rossmanith, Stefan wrote:
> Hi Doug,
> I have another question concerning WS-RM/RX.
> Scenario: The provider decides to terminate a sequence because of
> timeout (or other error situations).
>
> Is my understanding correct that the RMS in this case does not know
> which already sent messages were received successfully by RMD, because
> maybe some acks were lost and the RMS cannot request acks after RMD has
> terminated the sequence?
>
> If this is true, WS-RM only could be used for real applications if we
> have in addition a higher level protocol (e.g. a kind of transaction
> protocol or a mechanism on application level) which can handle this
> situation, i.e can proceed after this error situation in an appropriate
> way.
>
> I only want to know if my understanding fits to WS-RM intention ;-)
>
> One note to WS-RM 2005/02: In the AckRequest element the spec tells to
> use MessageNumber element but the schema tells to use
> MaxMessageNumberUsed Element...
> (I looked at the documents at
> http://msdn.microsoft.com/webservices/webservices/understanding/specs/de
> fault.aspx?pull=/library/en-us/dnglobspec/html/wsrmspecindex.asp )
>
> With kind regards,
> Stefan
>
>
> PS: unfortunately I cannot participate tomorrow and next week at WS-RX
> SC/TC, because of other dates.
>
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://feeds.feedburner.com/bloglines/pzf
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]