Re: MOAP v2

Doug,

I have a question regarding the following paragraph in
wseventing-moap.doc in your MOAP version 2 proposals:

9 WS-Eventing Metadata
An endpoint MAY indicate that it supports WS-Eventing, or its features,
by including the WS-Eventing EventSource or SubscriptionManager Policy
assertions within its WSDL. By doing so the endpoint is indicating that
the corresponding WS-Eventing operations are supported by that endpoint
even though they do not explicitly appear in its WSDL (i.e. the
WS-Eventing operations do not appear in the WSDL that MAY be retrievable
by using a WS-MetadataExchange GetWSDL to that endpoint).


The paragraph seems to suggest that the endpoint has a WSDL that is
different from the WS-Eventing WSDL, and the policy assertions are
attached to that WSDL. I wonder if these policy assertions can also be
attached to the WS-Eventing WSDL instead. There are two use cases for
this:

1) The endpoint has ONLY WS-Eventing WSDL. It is an event source and
subscription manager, but has no other services.

2) The endpoint has some services other than WS-Eventing, but the
endpoint chooses to consolidate all policy related to WS-Eventing in the
WS-Eventing WSDL. 

My questions are: if these use cases are supported; 2) if so, how the
WSDLs look like.

Thanks,

Li

Received on Tuesday, 2 March 2010 15:46:34 UTC