Unfortunately I don’t have the answer on how to do this, and after a bit of Googling it seems like I’m not the only one.
Getting VO’s from AMFPHP back into my Flex app as strongly typed objects is fine. Sending a single VO to a method in AMFPHP has me somewhat bamboozled though, given that this makes the Browser then only want to take a single parameter as well (which makes life a bit difficult for testing purposes).
My initial idea to get around this was to modify the service browser to detect when a parameter of a service method was actually a VO object. Then instead of letting the Browser just display a single textinput field (which would require an object with the same type as the VO you want to use - something I’ve got no idea how to do by text alone in the browser), each property of the VO would instead be displayed as it’s own individual textinput field.
Has anyone else been sending VO’s to AMFPHP and still made use of the Browser in their setup? Please drop us a comment if you have.
Recent Comments