[ 
https://issues.apache.org/jira/browse/CXF-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207848#comment-13207848
 ] 

Glen Mazza commented on CXF-4108:
---------------------------------

I may have overstepped by phrasing it as "by definition", rather, my impression 
was that Provider accepts any incoming SOAP requests, it's up to the 
implementor of the Provider to reject messages it doesn't like.

MessageContext.WSDL_OPERATION is not required by the JAX-WS specification (I 
can't find it even defined there), as the JAX-WS RI even stopped bothering to 
supply it 
(http://blog.vinodsingh.com/2009/03/how-to-get-operation-name-in-jax-ws.html); 
but if we are providing it, it should be provided either an accurate value 
(whatever the CXF runtime evaluated as the correct operation when matching 
against an SEI), or (arguably) not provided at all if it's going against a 
Provider interface (due to the CXF runtime presumably doing no 
operation-matching).

                
> Dispatch provider accepts any request
> -------------------------------------
>
>                 Key: CXF-4108
>                 URL: https://issues.apache.org/jira/browse/CXF-4108
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.5.2
>            Reporter: Zsolt Beothy-Elo
>         Attachments: request.txt, response.txt
>
>
> Start the server of the jaxws_dispatch_provider sample. Send a totally 
> unrelated request to the endpoint of the sample server. For the request 
> actually sent see attachment request.txt
> Expected behaviour: the service returns a fault with code = client  stating 
> an unknown operation was invoked.
> Actual behaviour: One of the service operations is called and normal response 
> is returned, see attachment response.txt
> Also replacing the empty soapAction values in the sample WSDL with distinct 
> values yields the same result. 
> Note: This behaviour can also be observed with other provider based services. 
> Of course here the business code might return a fault because the structure 
> of the request is not the expected one. Still already CXF should not accept 
> the requests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to