Skip to main content
Known Participant
November 10, 2008
Question

Is there a reason the XML decoder doesn't traverse up the schema stack when looking for a definition?

  • November 10, 2008
  • 2 replies
  • 700 views
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
This topic has been closed for replies.

2 replies

Known Participant
November 11, 2008
Thanks for that, I just wanted to make sure what I was seeing was in fact a bug and not done on purpose to suit some abstruse W3C rule I didn't know about :)

On Wed, Nov 12, 2008 at 4:05 AM, Peter Farland < member@adobeforums.com> wrote:

A new message was posted by Peter Farland in



Developers --

  Is there a reason the XML decoder doesn't traverse up the schema stack when looking for a definition?







Hi Josh,



 



The XMLDecoder does traverse the schema stack to find
definitions, just like the XMLEncoder, so you must have a particular scenario
that is causing a problem?



 



From Flex 2.0.1 HF2 onwards, a completely new implementation of WSDL/XML
Schema decoding was used the approach is entirely different so a
comparison won't show you much.



 



Pete



 









From: dznuts@gmail.com
[mailto: dznuts@gmail.com] On Behalf Of Josh McDonald

Sent: Sunday, November 09, 2008 9:50 PM

To: flexsdk-dev@adobeforums.com

Subject: Is there a reason the XML decoder doesn't traverse up the
schema stack when looking for a definition?







 



A new discussion was started by
Josh McDonald in



Developers --

  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












View/reply at Is there a reason the XML
decoder doesn't traverse up the schema stack when looking for a definition?


Replies by email are OK.

Use the unsubscribe
form to cancel your email subscription.













View/reply at Is there a reason the XML decoder doesn't traverse up the schema stack when looking for a definition?


Replies by email are OK.

Use the unsubscribe form to cancel your email subscription.





--
"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
Participating Frequently
November 11, 2008
<div class=Section1><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'>Hi Josh,<o:p></o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'><o:p> </o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'>The XMLDecoder does traverse the schema stack to find<br />definitions, just like the XMLEncoder, so you must have a particular scenario<br />that is causing a problem?<o:p></o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'><o:p> </o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'>From Flex 2.0.1 HF2 onwards, a completely new implementation of WSDL/XML<br />Schema decoding was used &#8211; the approach is entirely different so a<br />comparison won&#8217;t show you much.<o:p></o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'><o:p> </o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'>Pete<o:p></o:p></span></p><br /><br /><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";<br />color:#1F497D'><o:p> </o:p></span></p><br /><br /><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><br /><br /><div><br /><br /><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><br /><br /><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span<br />style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> dznuts@gmail.com<br />[mailto:dznuts@gmail.com] <b>On Behalf Of </b>Josh McDonald<br><br /><b>Sent:</b> Sunday, November 09, 2008 9:50 PM<br><br /><b>To:</b> flexsdk-dev@adobeforums.com<br><br /><b>Subject:</b> Is there a reason the XML decoder doesn't traverse up the<br />schema stack when looking for a definition?<o:p></o:p></span></p><br /><br /></div><br /><br /></div><br /><br /><p class=MsoNormal><o:p> </o:p></p><br /><br /><p class=MsoNormal style='margin-bottom:12.0pt'>A new discussion was started by<br />Josh McDonald in <br><br /><br><br /><b>Developers</b> --<br><br />  Is there a reason the XML decoder doesn't traverse up the schema<br />stack when looking for a definition?<br><br /><br><br />Hi guys,<br><br /><br><br />I'm wondering if there's a reason the XMLDecoder doesn't traverse back up the<br />schema stack when trying to find a type definition? I can't think of any, but<br />I'd like to get some feedback before filing a bug and submitting a patch? It<br />seems to be the source of a couple of bugs, one of which is keeping one of our<br />teams on Flex 2.<br><br /><br><br />Either Flex 2 didn't have a schema stack, or it did traverse it when looking<br />for definitions, but AFAIK the source to Flex 2's mx.rpc.* was never included<br />in the SDK, correct? Any chance I can get a copy of Flex 2's mx.rpc.xml.* tree<br />to compare against, or if I can get my question passed along in a hallway conversation<br />@ Adobe or something?<br clear=all><br /><br><br />Much appreciated,<br><br /><br><br />-Josh<br><br /><br><br />-- <br><br />&quot;Therefore, send not to know For whom the bell tolls. It tolls for<br />thee.&quot;<br><br /><br><br />Like the cut of my jib? Check out my Flex blog!<br><br /><br><br />:: Josh 'G-Funk' McDonald<br><br />:: 0437 221 380 :: <a href="mailto:josh@gfunk007.com">josh@gfunk007.com</a><br><br />:: <a href="http://flex.joshmcdonald.info/">http://flex.joshmcdonald.info/</a><br><br />:: <a href="http://twitter.com/sophistifunk">http://twitter.com/sophistifunk</a><br><br /><br><br /><o:p></o:p></p><br /><br /><div class=MsoNormal><br /><br /><hr size=2 width=200 style='width:150.0pt' align=left><br /><br /></div><br /><br /><p class=MsoNormal style='margin-bottom:12.0pt'>View/reply at <a<br />href="http://www.adobeforums.com/webx?13@@.59b6fc8b">Is there a reason the XML<br />decoder doesn't traverse up the schema stack when looking for a definition?</a><br><br />Replies by email are OK.<br><br />Use the <a<br />href="http://www.adobeforums.com/webx?280@@.59b6fc8b!folder=.3c060fa3">unsubscribe</a><br />form to cancel your email subscription.<o:p></o:p></p><br /><br /></div><br /><br /></div>