<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: XPath, xmlSearch, and Namespaces</title>
	<atom:link href="http://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/</link>
	<description>Thoughts, rants, and even some code from the mind of Barney Boisvert.</description>
	<lastBuildDate>Thu, 11 Sep 2014 09:58:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Clayton Davis</title>
		<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/comment-page-1/#comment-320863</link>
		<dc:creator>Clayton Davis</dc:creator>
		<pubDate>Sun, 02 Sep 2012 01:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://barneyb.com/barneyblog/?p=89#comment-320863</guid>
		<description>One of those ridiculous caveats of XML and XPath; thanks for the tip.  If Adobe cared to document or at least cross-reference a resource for XPath....</description>
		<content:encoded><![CDATA[<p>One of those ridiculous caveats of XML and XPath; thanks for the tip.  If Adobe cared to document or at least cross-reference a resource for XPath&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sher</title>
		<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/comment-page-1/#comment-122</link>
		<dc:creator>sher</dc:creator>
		<pubDate>Wed, 29 Jun 2005 23:54:49 +0000</pubDate>
		<guid isPermaLink="false">http://barneyb.com/barneyblog/?p=89#comment-122</guid>
		<description>internet advertising  internet advertising  free advertising  free advertising  advertising specialties  advertising specialties  home depot  home depot  work at home  work at home  home based business  home based business  internet marketing  internet marketing  network marketing  network marketing  search engine marketing  search engine marketing  better business bureau  better business bureau  home based business  home based business  business cards  business cards  shopping cart  shopping cart  ecommerce shopping cart  ecommerce shopping cart  shopping cart software  shopping cart software  house plans  house plans  white house  white house  full house  full house 
</description>
		<content:encoded><![CDATA[<p>internet advertising  internet advertising  free advertising  free advertising  advertising specialties  advertising specialties  home depot  home depot  work at home  work at home  home based business  home based business  internet marketing  internet marketing  network marketing  network marketing  search engine marketing  search engine marketing  better business bureau  better business bureau  home based business  home based business  business cards  business cards  shopping cart  shopping cart  ecommerce shopping cart  ecommerce shopping cart  shopping cart software  shopping cart software  house plans  house plans  white house  white house  full house  full house</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niklas Richardson</title>
		<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/comment-page-1/#comment-121</link>
		<dc:creator>Niklas Richardson</dc:creator>
		<pubDate>Wed, 18 May 2005 09:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://barneyb.com/barneyblog/?p=89#comment-121</guid>
		<description>Hi Barney,

I also bumped into an annoying bug in CFMX 6.1 when using XMLSearch and when you have an xPathString that is very long.

If the xPathString is too long you get an ArrayOutOfBound error thrown from ColdFusion.  Beautiful!

Here&#039;s the link and workaround:

http://www.prismix.com/blog/archives/2005/05/bug_in_xmlsearc.cfm</description>
		<content:encoded><![CDATA[<p>Hi Barney,</p>
<p>I also bumped into an annoying bug in CFMX 6.1 when using XMLSearch and when you have an xPathString that is very long.</p>
<p>If the xPathString is too long you get an ArrayOutOfBound error thrown from ColdFusion.  Beautiful!</p>
<p>Here's the link and workaround:</p>
<p><a href="http://www.prismix.com/blog/archives/2005/05/bug_in_xmlsearc.cfm" rel="nofollow">http://www.prismix.com/blog/archives/2005/05/bug_in_xmlsearc.cfm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barney</title>
		<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/comment-page-1/#comment-120</link>
		<dc:creator>Barney</dc:creator>
		<pubDate>Wed, 27 Apr 2005 19:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://barneyb.com/barneyblog/?p=89#comment-120</guid>
		<description>That wouldn&#039;t work in all cases.  What if you have two separate namespaces that both have an &#039;item&#039; element?

Much better to explicitly specify the namespace of the particular element you want, just specifying the default namespace is not at all obvious (at least wasn&#039;t to me).</description>
		<content:encoded><![CDATA[<p>That wouldn't work in all cases.  What if you have two separate namespaces that both have an 'item' element?</p>
<p>Much better to explicitly specify the namespace of the particular element you want, just specifying the default namespace is not at all obvious (at least wasn't to me).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raymond Camden</title>
		<link>https://www.barneyb.com/barneyblog/2005/04/27/xpath-xmlsearch-and-namespaces/comment-page-1/#comment-119</link>
		<dc:creator>Raymond Camden</dc:creator>
		<pubDate>Wed, 27 Apr 2005 18:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://barneyb.com/barneyblog/?p=89#comment-119</guid>
		<description>I ran into the same issue trying to parse RSS 1 and 2 in the same code. I ended up using this string, and it seemed to work just fine:

//*[local-name() = &#039;item&#039;]</description>
		<content:encoded><![CDATA[<p>I ran into the same issue trying to parse RSS 1 and 2 in the same code. I ended up using this string, and it seemed to work just fine:</p>
<p>//*[local-name() = 'item']</p>
]]></content:encoded>
	</item>
</channel>
</rss>
