This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
WS-Enumeration defines an output-only (ie. solicit-response) operation as follows: <wsdl:portType name="DataSource"> ... <wsdl:operation name="EnumerationEndOp" > <wsdl:output message="wsen:EnumerationEndMessage" wsa:Action=" http://schemas.xmlsoap.org/ws/2004/09/enumeration/EnumerationEnd"/> </wsdl:operation> </wsdl:portType> 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 it. Proposal: Remove this operation.
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0054.html
resolved 2009-03-1 with the following change: change EnumEndPort to EnumEndPortType