I've put a patch on bugzilla that fixes this issue for xindice.
I'll be updating bugzilla issue as soon as my mail gets through to xalan list.
In short:
* Use of reflection to work around incompatible changes in xalan
api is not the best way to fix the problem. Best way to fix it
is to fix the root of the problem, i.e. xalan api. * If best way is not achievable we will see what kludges we can plug
into our code base, or see when we can upgrade to latest xalan.
But it means trouble to users of older xindice or older
xalan. So here reflection will come in handy. * Passing null into the constructor, IIUC, will cause xpath to
fail when built-in xpath function is used (as function table
will be null). I might be mistaken here - have you run a test
suite with your patch & cvs xalan?Vadim
