Flash always canonicalizes namespace declarations in its internal representation. The meaning of the XML *should* be unaffected, but you might not get exactly the same text as you expect when you do toXMLString(). If, however, Flash is changing the meaning of your XML then you have found a bug.
Please post some code that shows the problem, so people can verify. Peter On 8/28/07, williamkusumo <[EMAIL PROTECTED]> wrote: > > Actually, it only happens with default namespace. > > I am trying to achieve this: > > <Root> > <Test xmlns="http://somenamespace"></Test> > </Root> > > I assign that to an XML object, set the default xml namespace, and it > always turns out like this: > > <Root xmlns="http://somenamespace"> > <Test></Test> > </Root> > > --- In [email protected] <flexcoders%40yahoogroups.com>, > "williamkusumo" <[EMAIL PROTECTED]> > wrote: > > > > Hi! > > > > I am assembling XML from strings. This XML has a default namespace and > > one custom namespace. The namespaces declarations have to be inside > > certain node. I notice Flex seems to be moving the namespaces around > > and putting them all into the root node. Is it possible to have it not > > do that? > > > > Appreciate the thoughts. > > > > >

