Hm. I don't see it that way.
Each list is really "chunked" into phases, no? So what does it mean
to specify an ordering declaratively, when the declared ordering is
not what will actually be realized at runtime?
It's misleading at best -- an outright lie, at worst.
Not sure I suggested a change to a programmatic API, unless that was
a logical consequence of something I said elsewhere. Was just
suggesting that we change/deprecate the name of a config varaible,
and to put it on a long finger, at that.
-Fred
On Apr 10, 2007, at 6:41 AM, Glynn, Eoghan wrote:
It's a bit more subtle that, I think. The individual interceptor lists
associated with each interceptor provider are indeed ordered, so the
list type is appropriate [IMO].
