[
https://issues.apache.org/jira/browse/CXF-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207839#comment-13207839
]
Daniel Kulp commented on CXF-4108:
----------------------------------
Likely should be null if the payload and/or soapaction cannot be mapped into a
binding operation from the WSDL. If it's not null, that's probably a bug.
Definitely shouldn't be some random operation from the wsdl. :-)
> 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
