Andrei Shakirin created CXF-5387:
------------------------------------
Summary: Relax SOAPAction check in SoapActionInInterceptor
Key: CXF-5387
URL: https://issues.apache.org/jira/browse/CXF-5387
Project: CXF
Issue Type: Improvement
Components: JAX-WS Runtime
Affects Versions: 2.7.7
Reporter: Andrei Shakirin
Assignee: Andrei Shakirin
I have a bit regression under 2.7.7 because of changes in
SoapActionInInterceptor
(https://fisheye6.atlassian.com/changelog/cxf?cs=1368559 )
SoapActionInInterceptor requires that the SOAPAction exactly matches to the
service operation.
The problem is that there are some scenarios where the proxies using Provider<>
API process requests from different clients with any SOAPAction.
There are two ways to fix the problem:
1. Introduce option "allowWrongSOAPAction" and tolerate wrong action only if a)
action is not specified in service model and b) flag is set
2. If action is not specified in ServiceModel, accept all SOAPAction (not only
empty ones)
Personally I prefer option (2), because current behavior is not intuitive:
in case of using proxy implementing Provider<> API: even if SOAP action has
reasonable value created by SoapUI (wsdl target namespace/operation name), CXF
responses with error "The given SOAPAction XXX does not match an operation",
because OperationInfo has empty action value, that doesn't match to request
soap action
--
This message was sent by Atlassian JIRA
(v6.1#6144)
