I do something similar from the Websphere Application Developer environment which I believe uses Axis2 as it's framework. (But it's integrated)
I generate the wsdl files bottom-up for my Service endpoints.
I have only had one minor issue and that is my objects all come in as a collection of Object Proxies, instead of using the Wsdl descriptions. This is not a huge problem as I can cast Object proxies to Object as opposed to the actual class and use it just fine. (got this answer here)
How are you making the call to the service?
I have had some trouble using the generated classes as the service caller, as it returns a different format than the MXML call. I will be playing with this this weekend to figure it out
If your wsdl is fine, how are you handling the result when you make the call for the ArrayList?
private var gridData:ListCollectionView;
private function result(e:ResultEvent):void
gridData = e.result
* The handleFaults() method is a very basic fault event handler method that
* displays an Alert with the error message.
public function faults(e:FaultEvent) : void
"A fault occurred contacting the server. Fault message is: "+e.fault.message);
wsdl="url of your wsdl"
The above works for Arrays of complex types. Let me know if you still have problems.
You can just bind the ArrayCollection like I have, straight to your Grid or Advanced Grid.
The only quirk is when you get objects out of the ArrayCollection for other things, you will have to cast them to Object instead of your class. This will work but it will not show compile time errors if there are any when operating on the Object.
I have yet to get this working from the generated Service.as class.