Next in thread → Next in month →

RE: [wsrp-wsia] [I#162] OperationNotSupportedOnThisNavigationalStateFault Needed

From
Rich Thompson <>
Date
2002-12-04T13:00:18+00:00
ID
Thread
RE: [wsrp-wsia] [I#162] OperationNotSupportedOnThisNavigationalStateFault Needed
I see .... of course there are hundreds of such possible bugs. The fault
Interface.OperationFailed is intended for such cases.

Rich Thompson


                                                                                                                   
                      Gil Tayar                                                                                    
                      <Gil.Tayar@webcol        To:                                   
                      lage.com>                cc:                                                                 
                                               Subject:  RE: [wsrp-wsia] [I#162]                                   
                      12/04/2002 12:00          OperationNotSupportedOnThisNavigationalSt    ateFault Needed       
                      AM                                                                                           
                                                                                                                   
                                                                                                                   



I think you _almost_ got the meaning. I agree - a _correct_ Consumer would
never call an operation not requested by the Producer in an interaction
URL.
But the spec (unfortunately!) has to allow for a buggy or incorrect
Consumer
which calls performBlockingInteraction when a performInteraction is called.
I would like to point out to that Consumer that it did something wrong
using
a specific fault.

-----Original Message-----
From: Rich Thompson [mailto:]
Sent: Wed, December 04, 2002 01:03
To: 
Subject: Re: [wsrp-wsia] [I#162]
OperationNotSupportedOnThisNavigationalStateFault Needed







Not sure what this would mean ... these operations are only called as a
result of user interacting with the entity's markup. What would a Consumer
reasonably do? If there is value, could it be covered by the
OperationFailed fault?

Rich Thompson
Interaction Middleware and Standards for Portal Server
IBM T.J. Watson Research Center
Yorktown Heights, NY
(914) 945-3225







                      Gil Tayar

                      <Gil.Tayar@webcol        To:

                      lage.com>                cc:

                                               Subject:  [wsrp-wsia]
[I#162]

                      12/01/2002 06:13
OperationNotSupportedOnThisNavigationalStateFault Needed
                      AM








Issue: 162
Status: Active
Topic: interface
Class: Minor_Technical
Raised by: Gil Tayar
Title: OperationNotSupportedOnThisNavigationalStateFault Needed
Date Added: 1-Dec-2002
Document Section:   v0.85/v5.3.1 & 5.3.2
Description:
Some Producers may use only performInteraction, or only
performBlockingInteraction, or just use getMarkup. Or maybe some Producers
support performInteraction only on some navstates,
performBlockingInteraction on others, and getMarkup on yet others. There is
no way to return a fault that indcates this


Gil Tayar
WebCollage



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
Next in thread → Next in month →