*weeps uncontrollably* ;-) Well, at least I know that I'm not going crazy.
I guess the reason it would work with a SOAP web service is before the object goes over the pipe it gets converted to SOAP XML. I wanted to use the VO to bind to to avoid having to write a whole seperate model just to bind to for validation. The easiest thing I guess would be to make a copy of the object before I send it. Thank you so much for your response! That's the sort of thing that should be in the documentation somewhere :-) --- In [email protected], Joe Berkovitz <[EMAIL PROTECTED]> wrote: > Unfortunately, bindings have the capability of making properties seem to > "disappear" from the standpoint of serialization. This happens because > when a binding is applied to an value object, the bindings system > invisibly replaces the var property with a getter/setter pair, and moves > the actual property value to an altered name. When the player > serializes the object, the property is no longer stored under its > expected name, and so it is not encoded properly in the stream.. > > So at the moment, bindings and serialization simply don't mix. This is > expected to clear up in Flex 2.0, from what I've heard. But in my view > it's one of the more serious problems with Flex as it stands. > > This causes a bunch of headaches, but it can be worked around. > Essentially, one has to avoid serializing any object which may have > active MXML bindings applied to it at the time. > > . . . . ...j Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
