[standard] Wrong behaviour of x:out inside x:forEach

2004-07-09 Thread Flavio Tordini
hi all, inside a x:forEach loop, i put an x:out that evaluates an XPath expression on a document which is not same of the x:forEach. The x:out seems to behave strangely. Take a look at following JSP: === %@ taglib prefix=x uri=http://java.sun.com/jsp/jstl/xml; % %@ taglib

using Node variables with JSTL XML tags

2004-09-08 Thread Flavio Tordini
hi all, I'm experimenting with the JSTL XML tags. I have a org.w3c.dom.Node variable and I'm trying to use the JSTL with it. Something like: x:out select=$node/@name/ The odd thing is that the XPath expression is evaluated relative the document root, not to the specified node. The following

Re: using Node variables with JSTL XML tags

2004-09-08 Thread Flavio Tordini
hi helios, Unfortunately it does not work. it gives the following error: Illegal argument evaluating XPath expression /*: java.lang.IllegalArgumentException: Node must be non-null for getDTMHandleFromNode Clearly the JSTL implementation is trying to use [EMAIL PROTECTED] as the variable name.

Re: using Node variables with JSTL XML tags

2004-09-08 Thread Flavio Tordini
hi all, In the list archive, I found that the same question has been asked in June e never answered: http://www.mail-archive.com/[EMAIL PROTECTED]/msg07315.html should I post to the dev mailing list? should I report a bug? please someone answer! flavio Flavio Tordini wrote: hi all, I'm

Re: using Node variables with JSTL XML tags

2004-09-08 Thread Flavio Tordini
the // operator, like: select=$doc//subnode. Otherwise, the only way (that I know of) to cd to a subnode, and therefore not have to give the full path is by using x:forEach. Chris -Original Message- From: Flavio Tordini [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 08, 2004 9:37 AM To: Tag

Re: using Node variables with JSTL XML tags

2004-09-09 Thread Flavio Tordini
with the xml jstl tags (forEach), so I've since moved on to using xslt. They're clearly not in a big hurry to fix these (what we would consider big) problems. Chris -Original Message- From: Flavio Tordini [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 08, 2004 10:36 AM To: Tag

Re: using Node variables with JSTL XML tags

2004-09-09 Thread Flavio Tordini
; At this point, the best thing to do would be to file a bug report: http://issues.apache.org/bugzilla/enter_bug.cgi?product=Taglibs Quoting Flavio Tordini [EMAIL PROTECTED]: hi Kris, I think Xalan does the right thing evaluating nodes = XPathAPI.selectNodeList(node, /@name); starting from

problem with fmt:formatDate

2004-10-14 Thread Flavio Tordini
locale would be much better than toString(). here's a sample JSP, you can test it with curl or wget: %@ taglib prefix=fmt uri=http://java.sun.com/jsp/jstl/fmt; % jsp:useBean id=now class=java.util.Date / fmt:formatDate value=${now} pattern=/ regards, flavio tordini

Re: problem with fmt:formatDate

2004-10-14 Thread Flavio Tordini
and scope). - If timeZone is null or empty, it is handled as if it was missing. - If this action fails to determine a formatting locale, it uses java.util.Date.toString() as the output format. So, it looks like it's at least behaving according to the spec... Quoting Flavio Tordini [EMAIL