axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] Updated: (AXIS-2692) soapaction value problem and related seialization problems under SOAP 1.2
Date Fri, 24 Aug 2007 14:39:31 GMT


Akitoshi Yoshida updated AXIS-2692:


the diff files

the modified source files

> soapaction value problem and related seialization problems under SOAP 1.2 
> --------------------------------------------------------------------------
>                 Key: AXIS-2692
>                 URL:
>             Project: Axis
>          Issue Type: Bug
>          Components: Basic Architecture
>    Affects Versions: 1.4
>         Environment: Win XP; JDK 1.4.2; Axis 1.4
>            Reporter: Akitoshi Yoshida
>             Fix For: current (nightly)
>         Attachments:
> The soapaction value should be set in the HTTP header SOAPAction for SOAP 1.1. But for
SOAP 1.2, it should be set in the action parameter of the content type. However, the current
implementation of org.apache.axis.transport.http.HTTPSender and CommonsHTTPSender sets this
value in the SOAPAction header for both SOAP 1.1. and 1.2.
> Concretely, when the soapaction property (Call.SOAPACTION_URI_PROPERTY ) in the MessageContext
is set to value "some-action", the current implementation writes for SOAP 1.2:
> Content-Type: application/soap+xml; charset=UTF-8
> ...
> SOAPAction: "some-action"
> But the correct behavior for SOAP 1.2 should be to have:
> Content-Type: application/soap+xml; charset=UTF-8; action="some-action"
> ...
> To correct this behavior, and need to be modified
so that the soapaction is serialized differently based on the SOAP version (i.e., based on
msgContext.getSOAPConstants() )
> A relevant problem for SOAP 1.2 is the SOAP with attachments. The current implementation
does not use the correct content type for the SOAP part under SOAP 1.2.
> To fix this problem, and need to be changed to take
the SOAP version in consideration.
> The diff files and the modified source files for those classes are included in the attached
zip file.
> Thank you.
> Best regards, Aki

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message