At 07:33 27.06.2002 -0700, [EMAIL PROTECTED] wrote: >On Thu, 27 Jun 2002, Ceki Gülcü wrote: > > > Let me just mention that using the TCL to keep track of the context is > > just one possible solution. Is there another place that keeps track of > > what thread is executing what web-application? Remember that the > > ContextRepositorySelector is implemented within the Container. It is > > not prevented from doing Container specific tricks. Just a possibility > > worth mentioning. > >I don't know any other way to pass/extract the information.
If there is an object that keeps track of contexts, you can pass it to the ContextualRepositorySelector when you instantiate it (the CRS). The CRS could ask that object to return "the current" context identifying the current web-application. Again, I do not know if this is possible, just speculating. >I think a BaseInterceptor/Valve/Coyte module that is aware of >the container should init the selector. The CRS should be set at the earliest occasion, but not earlier. :-) >Note that the ClassLoader that will become the TCL is available >as a property of Context ( in both tomcats ), you can use that >when setting up. > >If you can wait few more days, I'll implement something at Coyote >level - that would work on all present and future tomcats. That would be very nice. >Costin -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
