I'm not in front of flexbuilder now ... but that could be the issue ... cases where more than one returned showed up, but single instances didn't (now that I think about it).
However, I'm curious what you mean by "bracket notation". Could you clarify? Thanks for the tip, Paul On Nov 6, 2007 7:57 PM, Tracy Spratt <[EMAIL PROTECTED]> wrote: > > > > > > > > > > There ARE eserved names that cause problems, but I would not have expected > of those you found. > > > > The general solution is to use bracket notation to resolve the object. > > > > But before you try that, trace the xml using toXMLString(). Neither trace() > nor toString() handle simple nodes like you would expect. You problem may > just be in your debugging technique! > > > > Tracy > > > > > > ________________________________ > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Paul Dale > Sent: Tuesday, November 06, 2007 1:37 PM > To: [email protected] > Subject: [flexcoders] e4x oddness ... > > > > > > > > I have an XML file with nodes with name attributes. > > I'm trying to get the list of nodes that match a particular name="..." > > Using ... > trace(xmlConfig.descendants(Constants.fieldField).(attribute("name") > == "ccy") ); > > Returns the expected nodes ... but some other names don't work (even > though they are indeed in the XML). > > Are there reserved names or characters? > > The following names don't work > > comments, test, callput ... > > I don't see a common thread to what works and doesn't. > > Does anyone have a good e4x reference or any tips for things to watch > out for with it? > > Thanks in advance ... > > Paul > >
