Hi Edgar, just for curiosity have you try invoking the web service from a web page?
Yeah, I have and it works fine....
I seriously don't understand why event.result is null
And where do I find docs about this, you the ResultEvent object
or is it all trial and error?
Hi there Michael first and foremost, thanks for your interest I'll be browsing the docs now
the flex sdk I have installed is:
Version 3.3.0 build 4852
You're welcome Wilson, I'm curious about your problem. Once you find a solution which I hope will be very soon I strongly recommend you to post it here and mark it as answer so when someone else has the same issue it'll find a solution faster.
Have a good day.
Hi Wilson, something I forgot to recommend you was to use TraceTarget, maybe you've already tried this but in case you didn't, right after your mx:application tag add
And then run the app in debug mode and make the service call then take a look at the console to see what data is being sent and recieved from your app to your webservice.
Hi there Michael,
I'm now thinking that the problem is in how java generates the wsdl, consequentely the response.
This is the xml response I'm receiving from the .net services:
<?xml version="1.0" encoding="utf-8"?>
<HelloWorldResult>Hello Hello there, how are you today?</HelloWorldResult>
and this is what I'm getting from java
<?xml version="1.0" encoding="UTF-8"?>
<fromReturn xmlns="http://example">Hello world Wilson Edgar</fromReturn>
As you can see there are some differences, the reason why I say is because initially to test webservice (the java one) I created a client in java and it worked fine, but after reading your email, again, I decided to call the java webservice from a .net enviroment.... guess what, the return string is null.
So this is not a problem in flex but it's rather on the java side.
Althouhg now, I think, I understand better what's going on, I still don't have a solution :-(
I'm using Axis to expose the Java webservice