You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1.When I uses getResponse method on envelope, exception is thrown.
2.
3.
What is the expected output? What do you see instead?
-String is returned by my wcf service method as soap.
-Following exception is thrown:-
Code: s:Sender, Reason: The message could not be processed. This is most likely
because the action 'http://tempuri.org/IMyServiceOne/MethodOneTest' is
incorrect or because the message contains an invalid or expired security
context token or because there is a mismatch between bindings. The security
context token would be invalid if the service aborted the channel due to
inactivity. To prevent the service from aborting idle sessions prematurely
increase the Receive timeout on the service endpoint's binding.
What version of the product are you using? On what operating system?
-ksoap2-android-assembly-3.1.1-jar-with-dependencies.jar
Please provide any additional information below.
I'm using ksoap2 to call WCF Service from android with WSHttpBinding. When I
set the security mode to none in web.config file of my WCF Project (.NET) for
wsHttpBinding, my android code work fine. But when I remove this security mode
tag, as it WCF Service with wsHttpBinding, by default uses security mode
MESSAGE, my code does not work and thrown an exception in my android project. I
test the WCF Service in WCFTestClient. Its work fine. I’m sure that issue is
in my client that is android. Any help and guide always welcomed. Thanks in
advance.
Original issue reported on code.google.com by [email protected] on 31 Dec 2014 at 2:05
The text was updated successfully, but these errors were encountered:
The project is migrating to github. If you believe this issue is still valid
and should be tracked please file a new issue at
https://github.com/simpligility/ksoap2-android/issues
Original issue reported on code.google.com by
[email protected]
on 31 Dec 2014 at 2:05The text was updated successfully, but these errors were encountered: