On Monday, November 26, 2001, at 07:29 AM, Jason van Zyl wrote: > On 11/26/01 4:55 AM, "Costas Stergiou" <[EMAIL PROTECTED]> wrote: > >> As I understand from the code, each ApplicationTool is just init'ed >> before >> being added to the context, but the same instance of the tool is used >> for >> more than one requests withouth synchronization. So, if for one request >> a user is choosing one skin and at the same time another user uses a >> second >> skin, the the actual object instance that is added to the context of >> both >> requests, may be the same (so the mix up) >> >> Is that correct? Am I missing something here? >> Please, give me some feedback on this! > > I will take a look at this today. Thanks.
Looks like the problem is in the UIManager, or in the configuration. Only request-scoped pull-tools can get away without being thread-safe according to the docs for the Pull Service. <http://jakarta.apache.org/turbine/turbine-2/services/pull-service.html> UIManager is configured as a global tool and is not synchronized. I've never used the UIManager for anything, so take these suggestions with a grain of salt. It looks like you could solve the problem by configuring UIManager as a request scope tool, or by making it thread safe. -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
