tag:blogger.com,1999:blog-31425501.post115445586503459156..comments2008-04-22T12:38:18.572-05:00Comments on aftergeek: XMLSearch, XPath, and XML namespaces in ColdFusion...Jeremy Q. Afterglidenoreply@blogger.comBlogger7125tag:blogger.com,1999:blog-31425501.post-21027116095848750362008-04-22T02:58:00.000-05:002008-04-22T02:58:00.000-05:00Just in case someone else comes across this ... th...Just in case someone else comes across this ... the solution above did not work for me in CF8. (I did not try it in any other version.) Instead, I had to specify no namespace identifier.<BR/><BR/>For example, getting Google Picasa XML and performing an XPath search for "entry": <B>"/:feed/:entry"</B>.<BR/><BR/>To get the "media" namespace and the group element (media:group), use <B>"/:feed/:entry/media:group"</B>Robhttp://www.blogger.com/profile/17037398734725416371noreply@blogger.comtag:blogger.com,1999:blog-31425501.post-28104570380718281902008-03-06T15:28:00.000-06:002008-03-06T15:28:00.000-06:00Thanks, Ryan! We haven't moved to 8 yet, but I wil...Thanks, Ryan! We haven't moved to 8 yet, but I will definitely keep that in mind.Jeremy Q. Afterglidehttp://www.blogger.com/profile/05975135981872593591noreply@blogger.comtag:blogger.com,1999:blog-31425501.post-32230547850500060562008-01-18T13:11:00.000-06:002008-01-18T13:11:00.000-06:00We also had this problem, we are on CF8 now, so it...We also had this problem, we are on CF8 now, so it may be a little different, but the cleanest syntax we found was a namespace of '*'.<BR/><BR/><cfset MyArray = XMLSearch(MyXMLDoc, "//*:Response")%gt;Ryannoreply@blogger.comtag:blogger.com,1999:blog-31425501.post-57836335832844675142007-07-10T07:58:00.000-05:002007-07-10T07:58:00.000-05:00Great stuff - i also thought namespace stripping w...Great stuff - i also thought namespace stripping was the answer, but you've opened my eyes to a more elegant solution. Thank you!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-31425501.post-41141513462685828312007-05-08T10:35:00.000-05:002007-05-08T10:35:00.000-05:00Colin, actually I have run into that. Perhaps ther...Colin, actually I have run into that. Perhaps there are XML parsing performance improvements between MX 6 and 7 (we only just started to use 7 in production in the last few months where I work), but my experience with extremely large xml docs in 6 was similar to what you describe. Unfortunately I'm not aware of an elegant solution. I'm sure doing searches for explicit paths (as opposed to wildcard searches) would help quite a bit, but sometimes that can hurt the extensibility of the code.Jeremyhttp://www.blogger.com/profile/05975135981872593591noreply@blogger.comtag:blogger.com,1999:blog-31425501.post-51712899249003223992007-05-08T10:09:00.000-05:002007-05-08T10:09:00.000-05:00Hey,I too came to this solution after a lot of hea...Hey,<BR/><BR/>I too came to this solution after a lot of head scratching but now my source xml is getting quite large i'm finding XmlSearch really slow , have you experienced any performance problems?Colinnoreply@blogger.comtag:blogger.com,1999:blog-31425501.post-71567561425301584242007-02-28T10:37:00.000-06:002007-02-28T10:37:00.000-06:00Excellent solution.Excellent solution.Anonymousnoreply@blogger.com