You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "Steven E. Harris" <se...@panix.com> on 2007/05/01 03:05:56 UTC
SOAP action header
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?
Footnotes:
¹ http://www.w3.org/TR/soap12-part2/#ActionFeature
--
Steven E. Harris
Re: SOAP action header
Posted by "Steven E. Harris" <se...@panix.com>.
Dan Diephouse <da...@envoisolutions.com> writes:
> Seems like a bug. I created a JIRA for this and we'll fix it up for
> our next release!
Great. Thanks for following up.
--
Steven E. Harris
Re: SOAP action header
Posted by Dan Diephouse <da...@envoisolutions.com>.
Seems like a bug. I created a JIRA for this and we'll fix it up for our next
release!
https://issues.apache.org/jira/browse/CXF-633
Thanks,
- Dan
On 5/1/07, Steven E. Harris <se...@panix.com> wrote:
>
> 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?
>
>
> Footnotes:
> ¹ http://www.w3.org/TR/soap12-part2/#ActionFeature
>
> --
> Steven E. Harris
>
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog