> <report:attributes> > <report:attribute type="Source">TV Cap</report:attribute> > <report:attribute type="Source">HDTV</report:attribute> > <report:attribute type="Video Fmt">x264</report:attribute> > <report:attribute type="Video Fmt">720p</report:attribute> > <report:attribute type="Video Genre">Action/Adv</report:attribute> > <report:attribute type="Video Genre">Drama</report:attribute> > <report:attribute type="Language">English</report:attribute> > </report:attributes> > > The "report:attributes" node is returning as having 0 children, as > this debug output shows:
Hard to believe, since this sort of bug should be detected and corrected immediately during pre-release testing. So as a first step, I'd suggest modifying your code so it captures and/or prints out the incoming stream, so you can check that you are receiving the document you think you are. (Use a tee filter, or copy the stream into a file and parse it back in from there.) Another obvious question is whether there's another (empty) report:attributes element elsewhere in the document, and you're looking at that rather than this. Or there might be a flaw in your DOM-accessing code, which you didn't show us. Generally, it's a good idea to work up a small stand-alone example which demonstrates the problem -- that gives us something we can usefully debug, and if there is a problem in your code it often becomes much easier to see when isolated.
