That helps a lot. Seems a typical CF implementation of technology, so guess
next version will be fully compliant, ;-). Either that or they rather us
write it via Java.
Rob,
Good point. Might have to give that a try see what happens.
Thanks
-Kevin Marino
----------------------
Webmaster - HealthObjects
[EMAIL PROTECTED]
-----Original Message-----
From: Rob Rohan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 11:30 AM
To: CF-Talk
Subject: Re: Xpath expressions compliance
On Tue, 2004-02-10 at 07:50, Massimo Foti wrote:
> > Anybody know if Xpath in CF is fully compliant with all functions,
> > expressions,etc... Of the spec?
> >
> > I tried to use the value() function and got a not defined error. Its
> > certainly possible I implemented wrong, but I know how CF likes to do
> > partial implementations every so often ;)
> >
> The problem is that XmlSearch() works only with XPath expressions that
> returns an array of XML elelemts (NodeList). Anything else will throw an
> exception.
<side_note>
If you use XmlTransform and <cfsavecontent to do xml searches, however,
is uses Xerces so that is fully compatible with the same Xpath version
as Xerces XSLT (Xpath 1.0 I think). I would assume (as most coders hate
to write the same thing twice) that the XmlSearch is using the same sort
of process with a bit of MM intervention.
</side_note>
--
Vale,
Rob
Luxuria immodica insaniam creat.
Sanam formam viatae conservate!
http://www.rohanclan.com <http://www.rohanclan.com>
http://treebeard.sourceforge.net <http://treebeard.sourceforge.net>
http://ashpool.sourceforge.net <http://ashpool.sourceforge.net>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
