Tuesday, August 29, 2006

Working with Web Services in Adobe Flex 2

Flex 2 may be the hot new contender for King of the Hill in development frameworks, here's one example why

"Flex automatically does the work of transferring a class type when using remote objects (one of the many reasons to use remote objects). However, when using SOAP Web Services, strong typing is broken because the class associations aren't automatically transferred to internal Flex classes. It's unfortunate, and leaves a bit of a gap when trying to use strong typing and compile-time error checking

I figured there had to be a better way. After hunting around a bit, I came up with a solution that worked for my project. All that was needed was a generic object transfer utility to translate the incoming objects into typed classes that are created on the Flex side. Once the transfer objects have been written on the Flex side, then class introspection can be used to dynamically populate the values from untyped Web Service objects. Let me show you how I did it."





read more | digg story

1 comment:

Jack said...

Well written post on web services. I do agree with you all that was needed was a generic object transfer utility to translate the incoming objects into typed classes that are created on the Flex side.
electronic signature software

Some Fine Books

Blog Archive