I was afraid the following scenario would cause an infite
loop but decided to "try it anyway". What I was expecting didn't
happen....it actually appears to work and I'm pleasantly surprised.
Is this by design and is this okay to do? (I'm guessing this is a
result of the 'bindable property chain'?)
I have a form that pulls initial data down from a web service
method to populate user controls.
The user edits that data and sends the changes back using an
alternate web service method.
Minimum coding, typeing, etc...just an all around 'lazy way'
of doing it ;-)
Read the intial into the data model and populate the user
interface. Changes from the
user interface update the underlying data model AND changes
to the data model are
updated in the user interface.
Yes it is by design and is how you set up two-way binding.
Thanks for the encouraging response. I was afraid I had
stumbled onto an unsupported side affect (lol). After adding my
real webservices to the mix, it's really difficult to just call it
two-way databinding (more like intelligent mult-cast databinding
Believe it or not some folks have complained that this should
I'd be curious to find out what they propose would be
easier. Maybe some kind of graphical designer to create mx:Binding