On 1/6/11 6:48 PM, Alex Karasulu wrote:
Why not just inject the filter where you like by index into the filter
list - no need to move around interceptor order. If there is no add
with index position let's expose it. WDYT?
It would be more complicated. Inverting the interceptor is way simpler
and it works (I ran the tests)
In fact, considering what the collectiveAttribute does, it's quite
rational to have it before the subtree interceptor in the chain. The
only impacted request (and in a good way) is the search request.
Everything else is unchanged.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
