Re: Possible Tool Refresh bug : Resolved

[Peter Courcoux <pe...@courcoux.biz>]

Hi all,

The problem turned out to be that the skin properties were held in a
static property of the UIManager. 

I have submitted a patch to the dev list.

Thanks to Eric for his thoughts.

Regards,

Peter


On Fri, 2003-06-13 at 14:03, Peter Courcoux wrote:
> Hi all,
> 
> An update.
> 
> I have now put my application on turbine 2.3 and into production. 
> 
> The issue with skin crossover remains. If there are simultaneous users
> on different projects using different skins, pages are regularly
> rendered using all or part of a skin belonging to another user =:-|
> 
> Back to digging, but if anyone has any thoughts I would much appreciate
> hearing them.
> 
> Regards,
> 
> Peter 
> 
> 
> 
> On Thu, 2003-06-05 at 21:55, Peter Courcoux wrote:
> > Thanks Eric,
> > 
> > According to the docs, the UIManager should be capable of being used as
> > a session scoped tool and has the methods to use it as such. 
> > 
> > I am curious to know whether anyone else is using the UIManager as a
> > session scoped tool or has come across a similar problem with it or any
> > other session scoped tool.
> > 
> > I am currently in the process of testing my application with turbine
> > 2.3, in which the tool handling and in particular session tool handling
> > has been reworked by Quinton and Henning. I am hoping that the problem
> > will disappear, but realistically will not know until it has been run in
> > production for a few days (testing did not pick the problem up before).
> > 
> > Regards and thanks,
> > 
> > Peter
> > 
> > On Thu, 2003-06-05 at 21:19, Eric Emminger wrote:
> > > Peter
> > > 
> > > Peter Courcoux wrote:
> > > > Hi all,
> > > > 
> > > > I have been experiencing something that looks like a possible tool refresh or 
> > > > UIManager bug.
> > > > 
> > > > This is what is happening.
> > > > 
> > > > I am using t2.2.
> > > > 
> > > > I have users who can access different projects, one at a time. The
> > > > projects can have separate skins.
> > > > 
> > > > I have extended UIManager and made setSkin(User user) public, changed
> > > > TR.props to make the ui pull tool session scope and to refer to my
> > > > extended class.
> > > 
> > > I'm not sure, but this could be your problem. The original Turbine 
> > > UIManager is global scope and your extended version is session scope. 
> > > Changing the scope of the tool could be breaking the behaviour.
> > > 
> > > Eric
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
-- 
Peter Courcoux <pe...@courcoux.biz>

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org