Is saying "it's undefined" really good enough for things that are
"intuitive"? I mean, saying "division by zero" is undefined because
there is some formal reason for doing so.
I can see your point that if the order of specified interceptors are
governed by their internal Before/After settings that the config file
would conflict with the ordering of the "list". So, if the "config"
doesn't really define the order of the interceptors and it is desired
that be the case, then perhaps we should be using a construct that does
*not* imply an ordering such as Collection of List?
Cheers,
-Polar
Dan Diephouse wrote:
On 4/5/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
And furthermore, I was surprised (by trial and error, mind you) that if
you list two interceptors in a SpringBus bean interceptor property, that
they get installed in the reverse order than the order listed!
Ordering for interceptors is not currently defined unless you set the
before/after properties on your interceptor.
Regards,
- Dan
