2014/1/22 Mark Thomas <ma...@apache.org> > I've been looking at this some more with an eye to reducing code > duplication. I think the thread binding listener could be merged with > the ContainerListener. I can't see a good reason to keep them apart at > this point. With this in mind, the changes I'm planning are: > > - Add bindThread() and unbindThread() to the Context interface > - Add optional PA (as in callers can opt to use it if they wish) > support to bindThread() and unbindThread() > - Switch all the components currently implementing their own > bind/unbind methods to use these new context methods > - Switch container event type to use an enum > - Add bind and unbind events to this new enum > - Remove ThreadBindingListener > > The main benefit of this is that all the actions required on bind and > unbind will be in a single place rather than duplicated (sometimes > inconsistently) across the code base. > > +1
Rémy
