[ http://issues.apache.org/jira/browse/AXIS2-453?page=all ]
     
Davanum Srinivas resolved AXIS2-453:
------------------------------------

    Resolution: Fixed

Fixed AFAIK. Please try latest 0.95.

thanks,
dims

> Axis2 Code Generator for Eclipse generates code that does not quote 
> SOAPAction in HTTP Header and thus is not WS-I complient.
> -----------------------------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2-453
>          URL: http://issues.apache.org/jira/browse/AXIS2-453
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: Tools
>     Versions: 0.94
>  Environment: Windows / Java Development / Eclipse
>     Reporter: Ainsley Burdett
>     Priority: Minor

>
> According to the WS-I Basic Profile  (2004-08-24)  the value of SOAPAction in 
> the HTTP must be quoted and the reciver may respond with a fault if it is 
> not.  The stub code generated by the Eclipse Plugin from the WSDL does not do 
> this.  
> It could be argued that such quoting should be done in the core of AXIS2 not 
> just the tools, but there may be other issues at that level I am not aware 
> of.  At a minimum the tool should do this for HTTP bindings as its users are 
> least likely to be aware of this sort of issue.
> Extract from Profile...
> "R2744 A HTTP request MESSAGE MUST contain a SOAPAction HTTP header field 
> with a quoted value equal to the value of the soapAction attribute of 
> soapbind:operation, if present in the corresponding WSDL description. "
> "R2745 A HTTP request MESSAGE MUST contain a SOAPAction HTTP header field 
> with a quoted empty string value, if in the corresponding WSDL description, 
> the soapAction of soapbind:operation is either not present, or present with 
> an empty string as its value. "
> "R1119 A RECEIVER MAY respond with a fault if the value of the SOAPAction 
> HTTP header field in a message is not quoted. "

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to