On Tuesday, November 27, 2001, at 12:39 AM, Costas Stergiou wrote:
> Actually, when I mean "thread safe" I didn't mean "Java thread" > I meant "Request Safe" (actually it is thread safe also) but I don't > want to synchronize on the request tool of course. > But on a per-request basis, it is possible that the same instance of the > tool is being used at the same time for more than one requests > (threads); > since a tool is only being taken from the Pool service and init'ed but > there is no check that this tool is not being used by another thread. Here's how I understand it. Someone correct me if I get this wrong. If the UIManager is configured to be used in the request scope, then a new UIManager object will be instantiated with each request (or pulled from the pool). So you get one UIManager object per request, and that should fix your problem. If it is configured for any other scope (which it is by default) then multiple requests (and therefore multiple threads) will be accessing the same instance of the UIManager. In this case, the UIManager needs to be modified for thread-safety. -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
