This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6399 - Enumeration-EnumerationEnd violate WS-I BP
Summary: Enumeration-EnumerationEnd violate WS-I BP
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Enumeration (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-01-14 00:03 UTC by Doug Davis
Modified: 2009-04-21 21:33 UTC (History)
1 user (show)

See Also:


Description Doug Davis 2009-01-14 00:03:39 UTC
WS-Enumeration defines an output-only (ie. solicit-response) operation as 
<wsdl:portType name="DataSource"> 
  <wsdl:operation name="EnumerationEndOp" > 

WS-I Basic Profile R2303 says the following: 
4.5.2 Allowed Operations 
Solicit-Response and Notification operations are not well defined by WSDL 
1.1; furthermore, WSDL 1.1 does not define bindings for them. 

R2303 A DESCRIPTION MUST NOT use Solicit-Response and Notification type 
operations in a wsdl:portType definition. 

A solicit-response message reverses the interact between the service and 
the client. Typically, the client is responsible for initiating the 
interaction, but with solicit-response the service is sending an 
unsolicited message to the client.  BP determined that there wasn't any 
consensus on how to implement this (what would be the trigger mechanism 
for this message exchange, or how does the service initiate a connection 
with a client that might not allow incoming connections), thus BP banned 

Remove this operation.
Comment 2 Robert Freund 2009-03-11 17:28:08 UTC
resolved 2009-03-1 with the following change:
change EnumEndPort to EnumEndPortType