It is easy to show that it fails.
<mx:XML id="test">
<root>
<test1 desc="this little piggy does work &" />
<test2 desc="this little piggy does NOT work <li> for a list item at runtime" />
<test3 desc="this little piggy does NOT even compile " />
</root>
</mx:XML>
It works fine with loading the XML via HTTPService using the exact same XML - so I think it is a bug with the XML being converted at compile time. I think I remember there was a similar bug at the begining of time - like version 1.0 or something very very long ago.
J.
hmm interesting - I wonder if this happens because its xml source sucked in (ie it escaped characters get parsed when it gets sucked it)
what happens if you have that sort of stuff inline as opposed to pulled in from a file?
just curious...
PBHOn 7/6/06, Jonathan Bezuidenhout < [EMAIL PROTECTED]> wrote:Hi,
No nasty characters - just escaped ones.
It turns out that it is not that the string is too long - it is because it contains some escape sequences - it just happens to be that these strings are extra long.
Something like <li> makes it break - & works though. Also, something like < fails. If you have something like in your XML the app cannot even compile. All of these are perfectly good XML!
The above is using the <mx:XML source.../> construct where the XML is sucked in at compile time and the AS structure is created.
Jonathan
__._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
- Re: [flexcoders] Flex release version: XML attribute... Jonathan Bezuidenhout
Reply via email to