Hi,
marc fleury wrote:
> Also the main container "interceptors" should not be removed (i.e. if you
> put the acquisition after the synchronization the whole thing bombs).
>
> We might have "typeless" interceptors but their ordering is quite set in
> stone (CMT BMT etc etc). So the externalization is relevant to add
> additional custom interceptors in between or before and after but not the
> "basic EJB interceptors".
I think that we should give people the freedom
to configure the interceptor chain in whatever
way they want. Except for the ContainerInterceptor
who is always last and is not configured here.
Of course, such freedom also means that people are
free to shoot themselves in their feet :-(
But this *is* advanced configuration, and I think
that we should assume that people that are changing
this must know what they are doing.
In some cases it might make sense not to have all
the "basic EJB interceptors" in the chain. This
might be the case if a developer wrote a custom
interceptor that did the job of one of the basic
interceptors in some special way.
Best Regards,
Ole Husgaard.
