I recently had an issue from a customer regarding figuring out the correct syntax to get at a few nodes in an XML object that had namespaces using e4x. Now I don’t know about you, but if I don’t use e4x often, I forget things and get rusty. If your e4x-foo is weak, here are a few references that I found useful:
http://www.darronschall.com/weblog/archives/000223.cfm
(In fact Darren has a few e4x entries aside from this one.)
http://www.partlyhuman.com/blog/roger/as3-e4x-rundown
Hope this helps,
-Kyle
No Comments »
E4X is a very powerful and easy way to manipulate xml data in Flex.
Of course something so p[powerful can sometimes be confusing when it produces unexpected results.
<mx:XML format="e4x" id="myXML">
<order>
<item id=‘1′>
<menuName>burger</menuName>
<price>3.95</price>
</item>
<item id=‘2′>
<menuName>fries</menuName>
<price>1.45</price>
</item>
</order>
</mx:XML>
If you wanted to retrieve the price of the burger menuitem above, it is easily done with the e4x expression:
<mx:XML format="e4x" id="myXML">
<order>
<item id=’1′>
<menuName>burger</menuName>
<menuName>burger</menuName>
<price>3.95</price>
</item>
<item id=’2′>
<menuName>fries</menuName>
<price>1.45</price>
</item>
</order>
</mx:XML>
Then if you used the same expression, you actually would not get a value returned.
It is not obvious as to why this happens, but of course there is more than one way to skin a cat…
Here is an expression that will work:
myXML.item.menuName.(text()=="burger").parent().price;
Here is a link to a Flex Builder 2.0.1 project (compiled with SDK hotfix1) containing a sample demonstrating the solution described above.
No Comments »
Recent Comments