Hi,
I have some web service "wsdl first" with wsdl 1.1 and soap 1.2.
As specification states
http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/
<http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/> par. 4.2
SOAP Action
Use of the SOAPAction HTTP request header field is required when using
the SOAP 1.1 HTTP binding. The field-value of the SOAPAction HTTP request
header MUST either be the value of the [action] property enclosed in
quotation marks, or the empty value "". The latter case supports the ability
to obscure the [action] property through SOAP-level security mechanisms,
without requiring otherwise unnecessary transport-level security. Any other
value for SOAPAction results in an Invalid Message Addressing Property fault
(see 6.4.1 Invalid Addressing Header).
but CXF seems to handle faults in a non standard way:
SoapActionInInterceptor throws a general Fault instead of
was:InvalidAddressingHeader if the action attribute from http header
Content-Type is not correct (different value from the one inside the WSDL
soap:operation/@soapAction being called)
throw new Fault("SOAP_ACTION_MISMATCH", LOG, null, action);
I have also another question, if the soap:operation/@soapAction in the WSDL
is empty shouldn't it be calculated by CXF using the default action patter
as described here
http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#defactionwsdl11
<http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#defactionwsdl11> and
compared to http header action attribute inside Content-Type?
thank you.
regards,
Paolo
--
View this message in context:
http://cxf.547215.n5.nabble.com/SOAPAction-tp5718941.html
Sent from the cxf-user mailing list archive at Nabble.com.
