axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-1999) Add configuration setting to bypass the SOAP HTTP binding requirement of a SOAPAction header
Date Mon, 30 May 2005 17:21:55 GMT
     [ http://issues.apache.org/jira/browse/AXIS-1999?page=comments#action_66563 ]
     
Davanum Srinivas commented on AXIS-1999:
----------------------------------------

A patch would make it easy to make a decision :)

thanks,
dims

> Add configuration setting to bypass the SOAP HTTP binding requirement of a SOAPAction
header
> --------------------------------------------------------------------------------------------
>
>          Key: AXIS-1999
>          URL: http://issues.apache.org/jira/browse/AXIS-1999
>      Project: Axis
>         Type: Improvement
>   Components: Basic Architecture
>     Versions: 1.2
>  Environment: Irrelevant to this issue
>     Reporter: Jason Sweeney

>
> In the org.apache.axis.transport.http.AxisServlet.getSoapAction() method, when no HTTP
header is found for the name 'SOAPAction' (as defined in org.apache.axis.transport.http.HTTPConstants.HEADER_SOAP_ACTION),
the process faults and returns an error.  As you mention very clearly in the documentation
of this method, this is "technically" correct and respects the letter of the SOAP HTTP binding
specification.
> However, in the real world, there are numerous applications that would and could communication
SOAP message to an application exposing "web services" with Axis but that cannot configure
custom HTTP headers (usually because the protocol management is encapsulated in an external
library that never envisionned this possibility).  Since by everyone's admission this is really
a technicality of the specification and in real life almost no web services implementations
actually use the value of the SOAPAction header to set the service name information, we would
like the next version of Axis to offer a configuration setting to ignore this requirement
of the SOAP HTTP binding specification.
> A proposal would be to include a new global parameter named 'axis.requireSOAPActionHeader'
that would default to 'true', hence preserving the exact functional behavior of the current
version.  However, when set to false, the fault code of the getSoapAction() method mentioned
above would be simply skipped and the value associated to the SOAPAction header would be left
to 'null'.
> This simple configuration setting would allow many new business uses of the Axis framework
and extremely simply the incremental migration of the interaction of legacy systems with new
modern web service based systems.
> Thanks!

-- 
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


Mime
View raw message