You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Peter Courcoux <pe...@courcoux.biz> on 2003/06/04 17:29:19 UTC
Possible Tool Refresh bug
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.
Until selecting a project the skin is set to default.
When selecting a new project I call the static setSkin(User user, String
skin) method to set the User temp hashmap with the skin name then call
setSkin(User user) and then ui.refresh();
Most of the time each page is subsequently skinned correctly.
However, occasionally, a part of the page is formatted incorrectly,
maybe the background color of part of the page or a logo, may be
changed, not the whole skin. I think that this is only occurring when
there are users using different projects and when the system is under
some load. This does not show up as a problem as much as may be expected
because most users ( we have 20-60 logins per day ) are using the same
project and therefore the same skin.
As only the single project has its own skin and other (demo) projects
use the default skin, it is colors from the default skin which are being
picked up (possibly because it is the default skin, possibly because
it is the skin set for the demo projects).
Has anyone experienced anything similar. Is anyone else using the UIManager
pull tool in a session scope?
Any thoughts or pointers appreciated.
Regards,
Peter
--
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
Re: Possible Tool Refresh bug : Resolved
Posted by 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
Re: Possible Tool Refresh bug
Posted by Peter Courcoux <pe...@courcoux.biz>.
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
Re: Possible Tool Refresh bug
Posted by Peter Courcoux <pe...@courcoux.biz>.
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
Re: Possible Tool Refresh bug
Posted by Eric Emminger <er...@ericemminger.com>.
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