Question
Is there a reason the XML decoder doesn't traverse up the schema stack when looking for a definition?
Hi guys,
I'm wondering if there's a reason the XMLDecoder doesn't traverse back up the schema stack when trying to find a type definition? I can't think of any, but I'd like to get some feedback before filing a bug and submitting a patch? It seems to be the source of a couple of bugs, one of which is keeping one of our teams on Flex 2.
Either Flex 2 didn't have a schema stack, or it did traverse it when looking for definitions, but AFAIK the source to Flex 2's mx.rpc.* was never included in the SDK, correct? Any chance I can get a copy of Flex 2's mx.rpc.xml.* tree to compare against, or if I can get my question passed along in a hallway conversation @ Adobe or something?
Much appreciated,
-Josh
--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
Like the cut of my jib? Check out my Flex blog!
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: josh@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk
I'm wondering if there's a reason the XMLDecoder doesn't traverse back up the schema stack when trying to find a type definition? I can't think of any, but I'd like to get some feedback before filing a bug and submitting a patch? It seems to be the source of a couple of bugs, one of which is keeping one of our teams on Flex 2.
Either Flex 2 didn't have a schema stack, or it did traverse it when looking for definitions, but AFAIK the source to Flex 2's mx.rpc.* was never included in the SDK, correct? Any chance I can get a copy of Flex 2's mx.rpc.xml.* tree to compare against, or if I can get my question passed along in a hallway conversation @ Adobe or something?
Much appreciated,
-Josh
--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
Like the cut of my jib? Check out my Flex blog!
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: josh@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk
