I don't know if I have ever noticed this removal of comments, I'd need
to verify.
To iterate over nodes, use an e4x expression to return an XMLList, then
use a for loop. Or For Each, or For In. The docs have some more detail
and examples.
A list can also use XMLList as a dataProvider if
XML.ignoreComments = false;
--
Maciek Sakrejda
Truviso, Inc.
http://www.truviso.com
-Original Message-
From: dfalling [EMAIL PROTECTED]
Reply-To: flexcoders@yahoogroups.com
To: flexcoders@yahoogroups.com
Subject: [flexcoders] parsing complex xml
Date: Tue, 27 May 2008 22:09:41 -
I'm
Off the top of my head, If the root of your XML doc is configuration, you
want xmlObject.category as a list of category elements, not
xmlObject.configuration.category
-J
On Wed, May 28, 2008 at 8:09 AM, dfalling [EMAIL PROTECTED] wrote:
I'm trying to parse a complex xml file (a log4j config
Yeah, I should have mentioned that the server sending this file to me is
wrapping it in con, making that the root and configuration the only element.
On Tue, May 27, 2008 at 6:34 PM, Josh McDonald [EMAIL PROTECTED] wrote:
Off the top of my head, If the root of your XML doc is configuration,
I was trying both routes- dataprovider and and iterating.
dataProvider:
function dataReceived(data:XML):void
{
list.dataProvider = data.configuration.category;
}
With the above, nothing showed up in the list. The xml sample I provided in
my original email was all wrapped by a con tag by the
You should really be copying from your XML object into a flatter AS object
first - for binding and inline editing and whatnot as the XML objects
contain *much* voodoo that can bite you. But here's a quick example using a
datagrid rather than a list. As for updating and persisting the XML object,
6 matches
Mail list logo
