Bug 17321 - NPE from <x:out> with invalid select value
Summary: NPE from <x:out> with invalid select value
Status: RESOLVED FIXED
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-23 20:05 UTC by Hans Bergsten
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Bergsten 2003-02-23 20:05:46 UTC
The <x:out> action in 1.0.3 (and previous versions) throws an NPE if you give it
an invalid "select" attribute value, e.g.

  <x:out select="foo" />

java.lang.NullPointerException
	at org.jaxen.dom.DocumentNavigator$1.getFirstNode(DocumentNavigator.java:175)
	at org.jaxen.dom.DocumentNavigator$NodeIterator.(DocumentNavigator.java:823)
	at org.jaxen.dom.DocumentNavigator$1.(DocumentNavigator.java:172)
	at org.jaxen.dom.DocumentNavigator.getChildAxisIterator(DocumentNavigator.java:172)
	at org.jaxen.expr.iter.IterableChildAxis.iterator(IterableChildAxis.java:82)
	at org.jaxen.expr.DefaultStep.axisIterator(DefaultStep.java:139)
	at org.jaxen.expr.DefaultLocationPath.evaluate(DefaultLocationPath.java:188)
	at org.jaxen.expr.DefaultXPathExpr.asList(DefaultXPathExpr.java:107)
	at org.jaxen.BaseXPath.selectNodesForContext(BaseXPath.java:716)
	at org.jaxen.BaseXPath.selectSingleNodeForContext(BaseXPath.java:739)
	at org.jaxen.BaseXPath.stringValueOf(BaseXPath.java:281)
	at org.apache.taglibs.standard.tag.common.xml.XPathUtil.valueOf(XPathUtil.java:239)
	at
org.apache.taglibs.standard.tag.common.xml.ExprSupport.doStartTag(ExprSupport.java:102)
	at org.apache.taglibs.standard.tag.el.xml.ExprTag.doStartTag(ExprTag.java:103)
[...]
Comment 1 Pierre Delisle 2003-02-26 22:07:56 UTC
This requires some clarification to the spec to clearly state
the default context node associated with XPath expressions.

The expert group has approved this clarification and this will
be fixed in JSTL's upcoming maintenance release.
Comment 2 Pierre Delisle 2003-08-04 18:36:11 UTC
Fixed in 1.1.