This content has been marked as final. Show 8 replies
Sorry, the line in the example should be
In the doc it says INVOKE is an event on WebService but not an event on Operation. It seems like that's a bug in the doc. But yes, I've tried putting the listener on both the service and the operation, and it fails the same both ways.
you are right , I was confused too ;) ... ..
Have you tried to use
to get more infos with the debug output?
best regards and a nice weekend,
We're really stuck on this. How can a call to webService.send() fail to even get to the INVOKE stage? Can anybody else give me some ideas? Thanks.
Can you run this in debug mode and paste the output of the Error that is thrown? Or in no Error thrown?
1. No error is thrown at all. The web service has handlers for RESULT and FAULT and INVOKE and when it fails, none of those three get called. There's no error indication that I can find anywhere, the times when it fails.
2. Running it in the debugger changes the timing and the web service usually works.
I don't know if you're having the same problem, but when I was having timing issues, it was related to my calling of the web service before the WSDL was fully loaded.
In my case, the service was being called when my app initialized. My solution was to add a load handler to my service like so:
My loadWsdlHandler method then made the actual service call, secure in the knowledge that the WSDL was fully loaded.
The WSDL only needs to be loaded once before the first service call. If your service is first called by user interaction, then you could add the component in a disabled state, load the WSDL when the app initializes, and your load handler can enable the relevant control.