See below...
David Kensche wrote:
Hi, I found a bug. In org.apache.xindice.core.xupdate.XObjectImpl line 105 says:
return (NodeList) _xobj.nodeset();
which causes a ClassCastException. This fixes:
return _xobj.nodelist();
The Xalan API changed. Use early-model Xalan version with early model Xindice (e.g. 1.0). Use late-model Xalan version with late-model Xindice (e.g. CVS head or 1,1b1). See xindice-user archive for recent message on this subject.
I also have a question: When I specify an xpath expression with an attribute value like
String xpath = "//[EMAIL PROTECTED]>=0]";
Using index with type="long"? Value comparisons don't work correctly for any nummeric type of index and can cause unexpected results. See mailing lists archives and bugzilla.
or String xpath = "//[EMAIL PROTECTED]>='...']";
Using string comparisons? Check out xpath's specified behavior for comparisons. e.g. converts to number for >= comparisons. Current Xpath spec does not implement lexicographic string comparisons (comparisons are made instead by converting string to number). Future Xpath spec may call for lexicographic comparisons.
-Terry
I get no results. Isn't this implemented yet?
Thanks beforehand,
David
