I've been working with a RESTful service layer a lot recently that uses XML with a default namespace. In an ActionScript library project I have some delegate and model classes that natually use the default xml namespace directive. Once in a while I ran into a mysterious issue where the namespace doesn't seem to be applied, causing my XPath expressions to not find the values that are right there staring at me. When I stepped through the code I was able to see and trace out the complete XML value. I was baffled and found myself in a tailspin of trying random things to solve the issue. It turned out that all I needed to do was clean the projects (duh). I suspect that there's a small Flex compiler issue that messes with the application of namespaces. I'm curious if anyone else has had this issue and/or has a better explanation. If you've had this or a similar sounding issue, remember that it may not always be the code.
Mysterious Default XML Namespace Issue
February 9th, 2009 by Unknown Morphician
Hmm, very cognitive post.
Is this theme good unough for the Digg?
Thanks Sam, this fixed my issue. XML namespace support does seem buggy in Flex 3.