https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
Philippe Mouawad changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
--- Comment #9 from Philippe Mouawad 2011-11-20
20:55:47 UTC ---
Date: Sun Nov 20 20:55:08 2011
New Revision: 1204254
URL: http://svn.apache.org/viewvc?rev=1204254&view=rev
Log:
Bug 43294 - XPath Extractor namespace problems
First part: P
https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
--- Comment #8 from Sebb 2011-11-11 16:46:47 UTC ---
I'd not realised that we used any Xalan-specific classes, but I see now that we
use XPathAPI.
We should perhaps work towards removing that dependency ... seems like it is
not very effici
https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
--- Comment #7 from Philippe Mouawad 2011-11-11
13:56:05 UTC ---
The issue is that if we don't use Xalan, then we don't have the ability to
evaluate XPath expression without knowing their return type.
I mean in standard java XPath, evaluat
https://issues.apache.org/bugzilla/show_bug.cgi?id=43294
Sebb changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #6 from Sebb 2011-11-10 13
