On Thu, Sep 3, 2009 at 6:23 PM, Mukul Gandhi<gandhi.mukul@gmai...> wrote:
> Another idea that comes to my mind is, to provide a configurable
> option to users, to either use the minimal subset (which is the
> current implementation), or use full XPath 2.0 support, with
Apart from the points I mentioned, in the first post; regarding the
above point, we might make the XPath 2.0 subset (which is currently
available in Xerces-J) as a default option to users, and the full
XPath 2.0 processing, with PsychoPath selectable by user's via a
system property. Or should we make the defaults opposite?
We use this approach with assertions processing as well, where the
PsychoPath engine is default. The user's have option to select another
XPath 2.0 engine via the system property.
Any thoughts please about this, and the other points I mentioned earlier?
If these approaches add value to Xerces-J implementation, I'll be
happy to put effort on this (if I am allowed to :)).