This content has been marked as final. Show 5 replies
From a quick look at this WSDL the issue looks like we don't support SOAP encoded arrays of custom types (instead of built in types) very well and therefore this is a bug. A suggested work around may be to use a sequence of an unbounded number of elements instead of the deprecated soap encoded array for transmitting an Array.
Also, I'll enter a bug for the second observation 'you can't create a function without input, WebService won't parse the wsdl file ' as well.
The original problem ware predefined values which are not supported by flex WebService (<choice>).
But the operations with no input are really needed (I think).
I have a similar problem. I fail to see how to use the suggested work around ("a sequence of an unbounded number of elements"). Would it be possible to post an example of how Bill Brama's Directory Listing would look like using this strategy?
Let me know If you still want to see this example. The wsdl file has change since then and I'm using soap-enc array's instead. I didn't have time to play with wsdl. But... I have to refactor my code and if I manage to use "a sequence of an unbounded number of elements" I will post an example.
We have also changed our wsdl file as our problem was related to the use of xsd:import statements. See this blog-post by my colleague: