"ALRubinger" wrote : | | Nope. :) | | Interceptors are aspects; they encapsulate logic that runs across the core concerns of other components. So to dump them all in the same project would be counterproductive; we'd eventually build up a tangled mess of dependencies equivalent to the old "aspects" module of the AS. | I see what you mean. "ALRubinger" wrote : | So each interceptor should get its own component with release cycle. Then they can be plugged in at will. | As for this specific interceptor i don't see a reason why it needs to be in a new component. Infact the only reason this logic is going into an interceptor is to avoid repeated code all over the place, like what you say here: "ALRubinger" wrote : | Also, IMO we overuse interceptors. Oftentimes we leverage them just to break code out into some other space, | Given that this specific interceptor is going to put the right classloader on the thread, for use by components invoked by the container(s), i guess the core would be a right place for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247142#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...