RE: [wsrm] New Clariication Issue on Service enforcement of Reliabiliy agreement

Title: RE: [wsrm] New Clariication Issue on Service enforcement of Reliabiliy  agreement

Not a problem I believe:

The key thing to remember is that the receiver RMP only

gets its contract from the RMP sender, via the protocol.

In other words, received messages dictate what the receiver RMP should verify.

No prior agreement is needed on receiver side!

So there is no such thing as a sender RMP violating an agreement that the

receiver RMP was supposed to know beforehand.

If sender messages have no RM headers at all, no one is supposed to complain...

(we could call it "client is always right" policy !)

Of course, the WS endpoint might have specified its RM capabilities

e.g. in WSDL annotations, which may require that some RM features 

always be used (or not used) by clients. 

But at this point this is only for "information"

purpose, to help clients know what is supported on the end-point.

We do not mandate to enforce this at run-time.

Jacques

-----Original Message-----

From: Jeff Mischkinsky [mailto:]

Sent: Tuesday, February 24, 2004 5:40 PM

To: Sunil Kunisetty; 

Cc: wsrm

Subject: Re: [wsrm] New Clariication Issue on Service enforcement of

Reliabiliy agreement

At 11:46 AM 2/24/2004, Sunil Kunisetty wrote:

>Tom Rutt wrote:

>

> > I just realized a new issue for clarification:

> >

> > What is the expected service behavior when the client does not respect

> > the agreemen (i.e, contract) specified for a web service (conveyed

> > through whatever means)?

> >

> > In this case, is it required that the service send a fault OR is it up

> > to the service implementation to decide. This has conformance

> > implications for the service.

> >

>

>  It should be left to the implementation as we are not mandating the

>  'negotiation'  thingy.

I think refers to what happens at runtime, after the "'negotiation' 

thingy", however that occurs, has taken place. I.e. the client and the 

server have in some fashion (could be hard-coded, telephone exchange, some 

negotiation protocol exchange, etc.) and now one of them is breaking the 

contract.

cheers,

   jeff

> >

> > Example:

> >    a service that requires the use of callback (as specified in the

> > service contract) receives a message that uses another mechanism for

> > reply,    can the service still process the message OR it it required to

> > fault?

> >

> > --

> > ----------------------------------------------------

> > Tom Rutt                email: ; 

> > Tel: +1 732 801 5744          Fax: +1 732 774 5133

> >

> > To unsubscribe from this mailing list (and be removed from the roster 

> of the OASIS TC), go to 

> http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.

>

>

>To unsubscribe from this mailing list (and be removed from the roster of 

>the OASIS TC), go to 

>http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.

Jeff Mischkinsky                      

Consulting Member Technical Staff     +1(650)506-1975

Director, Web Services Standards      500 Oracle Parkway M/S 4OP9

Oracle Corporation                    Redwood Shores, CA 94065

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.