Steve,
Just to follow up on this, James and I are coordinating a solution between
Jaxen and JSTL. (I can replicate the problem; no need to post more
examples.) This will be fixed as soon as possible. Thanks for alerting
us to the error!
--
Shawn Bayern
Author, "JSP Standard Tag Library" htt
From: "Shawn Bayern" <[EMAIL PROTECTED]>
> > However if you write this as you've done...
> >
> > /root/a = 2
> >
> > Then this will be false. The quick reason for this is that there is more
> > than one element at /root/a.
> > The /root/a part of the expression evaluates to 2 element nodes. When
- Original Message -
From: "Shawn Bayern" <[EMAIL PROTECTED]>
> On Fri, 19 Apr 2002, James Strachan wrote:
>
> > OK I've convinced myself this isn't a Jaxen bug. Shawn - if you're
> > using the booleanValueOf() method in the tag, then this should
> > be fine, I've added an explicit test c
On Fri, 19 Apr 2002, James Strachan wrote:
> OK I've convinced myself this isn't a Jaxen bug. Shawn - if you're
> using the booleanValueOf() method in the tag, then this should
> be fine, I've added an explicit test case to Jaxen to prove it.
Yeah, I'm indeed using Jaxen's booleanValueOf().
>
ve of
how many elements are inside the .
Otherwise just the first matching node on the path /roo/a will be used,
which may not be what you mean.
James
- Original Message -
From: "Steve Morrison" <[EMAIL PROTECTED]>
To: "Tag Libraries Users List" <[EMAIL PROTECTED
t;Tag Libraries Users List" <[EMAIL PROTECTED]>
Sent: Thursday, April 18, 2002 10:40 PM
Subject: question about XPath tests
>
> I have a node in an XML doc I'd like to compare against.
> It's a number, say "1001".
>
>
> displays "true" or
I have a node in an XML doc I'd like to compare against.
It's a number, say "1001".
displays "true" or "false" correctly depending on if
the the node content is 1001 or not.
But this always is true:
true
no matter what is in the node.
I can use to set a variable and compare with
but t
