[
https://issues.apache.org/jira/browse/AXIS2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495742#comment-13495742
]
Ram commented on AXIS2-317:
---------------------------
Deepal,
But what if we don't have an access to modify the WSDL. Is there any workaround
call the Webservices for which the soapAction is not defined?
I'm using Axis2 and my generated stob contains the soapAction while they are
not defined in WSDL, hence getting "Service Not Found Exception".
Any help is really appreciated.
Thanks in Advance, and really sorry to treat JIRA as a discussion forum.
> WSDL2java generated classes throw "Operation Not found" when wsdl
> soapAction=""
> -------------------------------------------------------------------------------
>
> Key: AXIS2-317
> URL: https://issues.apache.org/jira/browse/AXIS2-317
> Project: Axis2
> Issue Type: Improvement
> Components: databinding
> Affects 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, please contact your JIRA administrators
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]
