[ http://issues.apache.org/jira/browse/AXIS2-317?page=all ]
Deepal Jayasinghe resolved AXIS2-317:
-------------------------------------
Fix Version: 1.0
Resolution: Fixed
All the time we generate SOAPAction whether it is present in wsdl or not , So
when you generate code all the time you have soap action is generated stub ,
and server side has the required mapping. Therefore this issue is not present
in current source code. If you still have the problem with current source or
RC2 please reopen the issue
> WSDL2java generated classes throw "Operation Not found" when wsdl
> soapAction=""
> -------------------------------------------------------------------------------
>
> Key: AXIS2-317
> URL: http://issues.apache.org/jira/browse/AXIS2-317
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: databinding
> Versions: 0.92
> Environment: java 5.0 , linux
> Reporter: trebor iksrazal
> Assignee: Ajith Harshana Ranabahu
> Priority: Minor
> Fix For: 1.0
>
> With rcp encoded wsdl's, often you'll put soapAction="" . With doc/lit, you
> need a soapAction defined, otherwise DispatchingChecker throws "Operation Not
> found" . An improvement would be some warning or error message identifying an
> empty string for soapAction does not work for doc/lit .
--
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
