[
https://issues.apache.org/jira/browse/AXIS2-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1897.
--------------------------------------
Resolution: Fixed
Issue shoud be fixed in the current SVN code base (re-open if not so)
> WSDL2Java adding SOAPAction
> ---------------------------
>
> Key: AXIS2-1897
> URL: https://issues.apache.org/jira/browse/AXIS2-1897
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: nightly
> Reporter: Dennis Sosnoski
> Assigned To: Amila Chinthaka Suriarachchi
> Priority: Blocker
>
> If the input WSDL uses <soap:operation soapAction=""/> in the <wsdl:binding>,
> WSDL2Java generates specific soapActions and uses these instead (as seen at
> runtime, but also in the output WSDL and in the services.xml). I don't know
> the rationale for this, but it seems likely to cause problems with other SOAP
> engines when they get SOAPAction headers they're not expecting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
