[jira] Commented: (CXF-633) SOAP 1.2 action header is sent incorrectly

["Steven E. Harris (JIRA)" <ji...@apache.org>]

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

Steven E. Harris commented on CXF-633:
--------------------------------------

I just tested this change this morning, and the (first) Content-Type header is now produced as requested above. Thanks for fixing this.

Issue CXF-687 remains open, as there are still two Content-Type headers produced.

> SOAP 1.2 action header is sent incorrectly
> ------------------------------------------
>
>                 Key: CXF-633
>                 URL: https://issues.apache.org/jira/browse/CXF-633
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0-M1, 2.0-RC
>            Reporter: Dan Diephouse
>            Assignee: Dan Diephouse
>             Fix For: 2.0
>
>
> From Steven Harris on the user list:
> My CXF client is using SOAP 1.2 over HTTP. I have specified a SOAP
> action in my WSDL for my one bound operation. This action value is
> getting sent as follows:
> ,----
> | POST /my/service/location HTTP/1.1
> | Content-Type: application/soap+xml; charset=UTF-8
> | action: "http://my/operation/action"
> | ...
> `----
> I would expect the SOAP 1.2 treatment of the action parameter to be
> adjoined to the Content-Type header, like this:
> ,----
> | POST /my/service/location HTTP/1.1
> | Content-Type: application/soap+xml; charset=UTF-8; action:="http://my/operation/action"
> | ...
> `----
> That's how AXIS2 does it, anyway, and it matches my reading of the
> SOAP 1.2 specification, Part 2, Adjuncts¹:
> ,----[ Section 6.5.2 SOAP Action Description ]
> | Many SOAP 1.2 underlying protocol bindings will likely utilize the
> | "application/soap+xml" media type (described in A. The
> | application/soap+xml Media Type) to transmit XML serializations of
> | SOAP messages. The media type specifies an optional action parameter,
> | which can be used to optimize dispatch or routing, among other things.
> `----
> Does CXF's use of the "action" header in the first example above
> conform to SOAP 1.2?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.