Re: issue 6435: v7 of the WS-Eventing state tables

Gilbert Pilz <gilbert.pilz@oracle.com> wrote on 01/25/2010 07:54:52 PM:
> - SubscribeRequest/Active and SubscribeRequest/End boxes for Source:
> I think those should be the same as the "Idle" state because 
> regardless of the state of any  Subscription, the way a source deals
> with a Subscribe Request needs to be the same.
> 
> I don't think I fully communicated what I thought it meant for 
> something in the "Active" state to get a Subscribe request. Suppose 
> the Event Source identified subscriptions using reference 
> parameters. What happens if you get a Subscribe request that has 
> those reference parameters and their value refers to an already 
> "Active" subscription?

I think there are really two ways this incoming message could be 
interpretted.
1) its targeted to an event source and not a subscription manager.  In 
which case
the current state is "Idle".
2) its targeted to a subscription manager and not an event source.  In 
which case
it should generate some kind of fault because there is no Subscribe() 
operation
defined for subscription managers.  But I don't think this is a fault for 
ws-e
to define.  This would most likely be a WSA fault - like unknown action or 
something.

I think its probably up to the implementation to decide what role its 
acting for
each message and the best our state table can do is cover the case of it 
being
sent to an event source.

-Doug