[EMAIL PROTECTED] wrote:
>
> Note that normally the need for sorting can be determined statically in
> WalkerFactory. The problem is caused by a filter expression which can
> start with either a variable or an extension, in which case, we can't tell
> if sorting needs to be done until runtime.
>
Is the expression a filter expression because in is proceeded by the variable.
i.e. is $table/row-set/row the filter expression or is row-set/row the filter
expression and the sorting can not be determined because of the it is not a
pure XPath statement ?? Hope I am being clear here, maybe a brief explanation
of what a filter expression is may help.
I need to dig deeper into the whole transformation process, but why can't the
DTM support an interface such as hasSupportFor(int option). Then when
WalkerFactory is determining if a sorted walker is required the document
can be asked if it supports a specific feature. similar to the canCrissCross()
method. Does this tie XPath to a particular document implementation ??
JG
