<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/jaxen/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/jaxen/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 22 Dec 2003 09:31:42 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/jaxen/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Bad order with selectNodes //something</title><link>https://sourceforge.net/p/jaxen/bugs/19/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;According the documentation of BaseXPath.selectNodes, &lt;br /&gt;
&amp;amp;quot;nodes will be returned in document-order&amp;amp;quot; unless I'm &lt;br /&gt;
&amp;amp;quot;using XPath expressions involving the union operator&amp;amp;quot;. &lt;br /&gt;
But it seems that //somthing expressions return the result &lt;br /&gt;
not in document order. E.g for this XML:&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;a&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;x&amp;amp;gt;1&amp;amp;lt;/x&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;b&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;x&amp;amp;gt;2&amp;amp;lt;/x&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;x&amp;amp;gt;3&amp;amp;lt;/x&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/b&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;x&amp;amp;gt;4&amp;amp;lt;/x&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/a&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;XPath expression //x will return the nodes in order 1, 4, &lt;br /&gt;
2, 3.&lt;/p&gt;
&lt;p&gt;I have tried it with both 1.0 FCS and the 1.1 beta.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dániel Dékány</dc:creator><pubDate>Mon, 22 Dec 2003 09:31:42 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2b2058282e98e2b7ab5f9afaf9db352cd694ce93</guid></item><item><title>Extension list in MANIFEST.MF incorrect</title><link>https://sourceforge.net/p/jaxen/bugs/18/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The Extension list in the MANIFEST.MF is comma-&lt;br /&gt;
separated.  This causes problems with Tomcat when &lt;br /&gt;
deploying a WAR with jaxen included because Tomcat &lt;br /&gt;
expects the list to be space-separated.  This results in &lt;br /&gt;
an IllegalArgumentException.  It appears from the JAR &lt;br /&gt;
specification that this list should indeed be space-&lt;br /&gt;
separated.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gerry Woods</dc:creator><pubDate>Tue, 19 Aug 2003 00:32:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net75dae7e67c771e94a5ce8ae3416afd4c8b66bc3c</guid></item><item><title>selectNodes in DOM</title><link>https://sourceforge.net/p/jaxen/bugs/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Unlike selectSingleNode, the Nodes in the List are not &lt;br /&gt;
updateable.  I was hoping to make mass-updates like...&lt;/p&gt;
&lt;p&gt;Iterator iter = nodeList.iterator();&lt;br /&gt;
while (iter.hasNext()) {&lt;br /&gt;
Node node = (Node)iter.next();&lt;br /&gt;
node.setNodeValue(newValue);&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;If this is not a bug, is there a different way to achieve &lt;br /&gt;
this easily?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 23 Jul 2003 17:14:01 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcccdad9b5e4d0d0b843e3766823bf5f1dd473b3f</guid></item><item><title>XPath function throws exception when using NamespaceContext</title><link>https://sourceforge.net/p/jaxen/bugs/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The API documentation say, about the getFunction method&lt;br /&gt;
of FunctionContext :&lt;br /&gt;
&amp;amp;quot; Parameters:&lt;br /&gt;
namespaceURI - the namespace uri to which the prefix&lt;br /&gt;
parameter is bound in the xpath expression. If the&lt;br /&gt;
function call expression had no prefix, the namespace&lt;br /&gt;
uri is null. &amp;amp;quot;&lt;/p&gt;
&lt;p&gt;Here, the last sentence is important.&lt;/p&gt;
&lt;p&gt;That should be ok for native XPath functions, however,&lt;br /&gt;
when using a namespace context, this behaviour is not&lt;br /&gt;
followed :&lt;/p&gt;
&lt;p&gt;SimpleNamespaceContext nsContext = new&lt;br /&gt;
SimpleNamespaceContext();&lt;br /&gt;
// Add all namespace declarations from the node&lt;br /&gt;
nsContext.addElementNamespaces(this.xpath.getNavigator(),&lt;br /&gt;
node);&lt;br /&gt;
this.xpath.setNamespaceContext(nsContext);&lt;/p&gt;
&lt;p&gt;When this.xpath is evaluated, native XPath functions&lt;br /&gt;
are unreachable if the node or one of its ancestor&lt;br /&gt;
defines the default ns (xmlns=&amp;amp;quot;foo&amp;amp;quot;)&lt;br /&gt;
This cause an exception : &lt;br /&gt;
org.jaxen.UnresolvableException: Function :string&lt;br /&gt;
(that's the same for any function, of course)&lt;/p&gt;
&lt;p&gt;I read the code of SimpleFunctionContext, and it seems&lt;br /&gt;
to ignore what is indicated in the FunctionContext API,&lt;br /&gt;
that is to say that no test of the presence of the&lt;br /&gt;
prefix is done;&lt;br /&gt;
Maybe the bug could be correct by testing it.&lt;/p&gt;
&lt;p&gt;On the user side, this bug can be avoid by adding this&lt;br /&gt;
code after nsContext.addElementNamespaces(...) :&lt;/p&gt;
&lt;p&gt;// reset ns declaration for default ns&lt;br /&gt;
nsContext.addNamespace(&amp;amp;quot;&amp;amp;quot;, null);&lt;/p&gt;
&lt;p&gt;But this is not enough because the default ns is also&lt;br /&gt;
ignore for other usage than function call resolution.&lt;/p&gt;
&lt;p&gt;Cordialement,&lt;br /&gt;
Philippe Poulard&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 02 Jul 2003 09:41:29 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net942f95dfae42417ee7a3a48fc4be229aa19c3173</guid></item><item><title>Jaxen does not compile with GUMP</title><link>https://sourceforge.net/p/jaxen/bugs/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The problem is that the interface in JDOM has changed&lt;br /&gt;
for the getParent() method.  There is no class named&lt;br /&gt;
Parent, and it returns an Element instead.  In fact,&lt;br /&gt;
the JDOM published API docs list this as the case.  The&lt;br /&gt;
official compilation error is this&lt;br /&gt;
(http://cvs.apache.org/builds/gump/latest/jaxen.html):&lt;/p&gt;
&lt;p&gt;Buildfile: build-legacy.xml init: [echo] -----------&lt;br /&gt;
Jaxen 1.0-FCS [2002] ------------ clean: prepare:&lt;br /&gt;
[mkdir] Created dir: /home/rubys/jakarta/jaxen/build&lt;br /&gt;
[mkdir] Created dir:&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/classes [mkdir] Created&lt;br /&gt;
dir: /home/rubys/jakarta/jaxen/build/classes/main&lt;br /&gt;
[mkdir] Created dir:&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/classes/test [mkdir]&lt;br /&gt;
Created dir:&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/classes/samples [mkdir]&lt;br /&gt;
Created dir: /home/rubys/jakarta/jaxen/build/src&lt;br /&gt;
[mkdir] Created dir:&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main [mkdir]&lt;br /&gt;
Created dir: /home/rubys/jakarta/jaxen/build/src/test&lt;br /&gt;
[mkdir] Created dir:&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/samples&lt;br /&gt;
prepare.core: [copy] Copying 179 files to&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main [copy] Copied&lt;br /&gt;
4 empty directories to&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main compile.core:&lt;br /&gt;
internal.compile: [javac] Compiling 170 source files to&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/classes/main [javac]&lt;br /&gt;
This version of java does not support the classic&lt;br /&gt;
compiler; upgrading to modern prepare.dom4j:&lt;br /&gt;
compile.dom4j: internal.compile: prepare.jdom: [copy]&lt;br /&gt;
Copying 4 files to&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main compile.jdom:&lt;br /&gt;
[echo] support.jdom true internal.compile: [javac]&lt;br /&gt;
Compiling 3 source files to&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/classes/main [javac]&lt;br /&gt;
This version of java does not support the classic&lt;br /&gt;
compiler; upgrading to modern [javac]&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main/org/jaxen/jdom/DocumentNavigator.java:234:&lt;br /&gt;
incompatible types [javac] found : org.jdom.Parent&lt;br /&gt;
[javac] required: org.jdom.Element [javac] current =&lt;br /&gt;
current.getParent(); [javac] ^ [javac]&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main/org/jaxen/jdom/DocumentNavigator.java:461:&lt;br /&gt;
incompatible types [javac] found : org.jdom.Parent&lt;br /&gt;
[javac] required: org.jdom.Element [javac] element =&lt;br /&gt;
((Text)context).getParent(); [javac] ^ [javac]&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main/org/jaxen/jdom/DocumentNavigator.java:473:&lt;br /&gt;
incompatible types [javac] found : org.jdom.Parent&lt;br /&gt;
[javac] required: org.jdom.Element [javac] element =&lt;br /&gt;
((Comment)context).getParent(); [javac] ^ [javac]&lt;br /&gt;
/home/rubys/jakarta/jaxen/build/src/main/org/jaxen/jdom/DocumentNavigator.java:477:&lt;br /&gt;
incompatible types [javac] found : org.jdom.Parent&lt;br /&gt;
[javac] required: org.jdom.Element [javac] element =&lt;br /&gt;
((ProcessingInstruction)context).getParent(); [javac] ^&lt;br /&gt;
[javac] 4 errors BUILD FAILED&lt;br /&gt;
/home/rubys/jakarta/jaxen/build-legacy.xml:249: Compile&lt;br /&gt;
failed; see the compiler error output for details.&lt;br /&gt;
Total time: 10 seconds&lt;/p&gt;
&lt;p&gt;Please remove all use of the class org.jdom.Parent, and&lt;br /&gt;
just use the Element class.  That would be best.&lt;/p&gt;&lt;/div&gt;</description><pubDate>Tue, 03 Jun 2003 12:49:27 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net3e1a1c6649534cea96ecee86f66977ba321f0046</guid></item><item><title>Date does not work for a Date data type attribute.</title><link>https://sourceforge.net/p/jaxen/bugs/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;See attached example program in the zip file.  A .bat &lt;br /&gt;
file has been created to compile and run the &lt;br /&gt;
JaxenDateBug application showing the problem.  Also in &lt;br /&gt;
the zip is a sample xml file named &lt;br /&gt;
GraphosBLS.xml.JUnit20 &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul H. Roubekas</dc:creator><pubDate>Fri, 21 Feb 2003 20:02:38 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf4b1f5c5d705889d3d76a686c305a4e878f12d41</guid></item><item><title>xpath result error with jdom</title><link>https://sourceforge.net/p/jaxen/bugs/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The xpath result set when using jdom is incorrect when &lt;br /&gt;
using the text() function. However, when using the DOM &lt;br /&gt;
implementation returns the correct result set.&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;root&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;data&amp;amp;gt;1&amp;amp;lt;/data&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/root&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;xpath expr  //data/text()&lt;/p&gt;
&lt;p&gt;JDOM:&lt;/p&gt;
&lt;p&gt;XPath path = new JDOMXPath(expr);&lt;br /&gt;
List list = path.selectNodes(root);  // root is a jdom &lt;br /&gt;
element&lt;/p&gt;
&lt;p&gt;List is empty.&lt;/p&gt;
&lt;p&gt;DOM:&lt;/p&gt;
&lt;p&gt;XPath path = new DOMXPath(expr);&lt;br /&gt;
List list = path.selectNodes(root);  // root is a w3c &lt;br /&gt;
dom element&lt;/p&gt;
&lt;p&gt;List contains one element&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 05 Feb 2003 21:12:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4830e881e71ef530d4400146f7c2e4bcd7ceff7a</guid></item><item><title>xpath result error with jdom</title><link>https://sourceforge.net/p/jaxen/bugs/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The xpath result set when using jdom is incorrect when &lt;br /&gt;
using the text() function. However, when using the DOM &lt;br /&gt;
implementation returns the correct result set.&lt;/p&gt;
&lt;p&gt;&amp;amp;lt;root&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;data&amp;amp;gt;1&amp;amp;lt;/data&amp;amp;gt;&lt;br /&gt;
&amp;amp;lt;/root&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;xpath expr  //data/text()&lt;/p&gt;
&lt;p&gt;JDOM:&lt;/p&gt;
&lt;p&gt;XPath path = new JDOMXPath(expr);&lt;br /&gt;
List list = path.selectNodes(root);  // root is a jdom &lt;br /&gt;
element&lt;/p&gt;
&lt;p&gt;List is empty.&lt;/p&gt;
&lt;p&gt;DOM:&lt;/p&gt;
&lt;p&gt;XPath path = new DOMXPath(expr);&lt;br /&gt;
List list = path.selectNodes(root);  // root is a w3c &lt;br /&gt;
dom element&lt;/p&gt;
&lt;p&gt;List contains one element&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 05 Feb 2003 18:41:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net66a1c60b71fa0790ee149a6ce00117cf33fa0c09</guid></item><item><title>Stack overflow FunctionCallException</title><link>https://sourceforge.net/p/jaxen/bugs/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;we get a stack over flow in FunctionCallException.printStackTrace( PrintStream s )&lt;/p&gt;
&lt;p&gt;at java.lang.Throwable.printStackTrace(Throwable.java:451)&lt;br /&gt;
at org.jaxen.FunctionCallException.printStackTrace(FunctionCallException.java:96)&lt;br /&gt;
at java.lang.Throwable.printStackTrace(Throwable.java:451)&lt;br /&gt;
at org.jaxen.FunctionCallException.printStackTrace(FunctionCallException.java:96)&lt;br /&gt;
at java.lang.Throwable.printStackTrace(Throwable.java:451)&lt;/p&gt;
&lt;p&gt;Ok, our function shouldn't throw an exception. But to fix our bug, it would be nice to see the original &lt;br /&gt;
exception. Since Tomcat calls up printStackTrace with an PrintStream there is no easy workaround.&lt;/p&gt;
&lt;p&gt;By the Way, thank you for the great jasper package!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 03 Feb 2003 14:17:43 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netfa13d934ef59ef5aa2e586cc2dfc687ec14536f2</guid></item><item><title>boolean NaN evaluation</title><link>https://sourceforge.net/p/jaxen/bugs/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When a NaN value is evaluated as a boolean, false &lt;br /&gt;
should be returned. Instead, true is returned. This is &lt;br /&gt;
caused by the following code in BooleanFunction.java &lt;br /&gt;
(line 120):&lt;/p&gt;
&lt;p&gt;if ( d == 0 || d == Double.NaN )&lt;/p&gt;
&lt;p&gt;which should be replaced by&lt;/p&gt;
&lt;p&gt;if ( d == 0 || Double.isNaN(d) )&lt;/p&gt;
&lt;p&gt;Ruud Diterwich&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ruud Diterwich</dc:creator><pubDate>Mon, 27 Jan 2003 08:43:24 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net49d0416ffe206c93e4ced69a5c93eaea74e17c49</guid></item></channel></rss>