[jira] Created: (TAPESTRY-320) "client" persistent properties are shared between users

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TAPESTRY-320) "client" persistent properties are shared between users

JIRA tapestry-dev@jakarta.apache.org
"client" persistent properties are shared between users
-------------------------------------------------------

         Key: TAPESTRY-320
         URL: http://issues.apache.org/jira/browse/TAPESTRY-320
     Project: Tapestry
        Type: Bug
    Reporter: Howard M. Lewis Ship


This is caused by a number of factors:
- The service model for tapestry.persist.ClientPropertyPersistenceStrategy was primitive, not threaded
- The initialize method was not named properly

The end result is that a single ClientPropertyPersistenceStrategy instance was being shared between all users, so that changes to state by one user would be seen in later requests by all users.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (TAPESTRY-320) "client" persistent properties are shared between users

JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-320?page=all ]

Howard M. Lewis Ship reassigned TAPESTRY-320:
---------------------------------------------

    Assign To: Howard M. Lewis Ship

> "client" persistent properties are shared between users
> -------------------------------------------------------
>
>          Key: TAPESTRY-320
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-320
>      Project: Tapestry
>         Type: Bug
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> This is caused by a number of factors:
> - The service model for tapestry.persist.ClientPropertyPersistenceStrategy was primitive, not threaded
> - The initialize method was not named properly
> The end result is that a single ClientPropertyPersistenceStrategy instance was being shared between all users, so that changes to state by one user would be seen in later requests by all users.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (TAPESTRY-320) "client" persistent properties are shared between users

JIRA tapestry-dev@jakarta.apache.org
In reply to this post by JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-320?page=all ]
     
Howard M. Lewis Ship closed TAPESTRY-320:
-----------------------------------------

    Resolution: Fixed

> "client" persistent properties are shared between users
> -------------------------------------------------------
>
>          Key: TAPESTRY-320
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-320
>      Project: Tapestry
>         Type: Bug
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> This is caused by a number of factors:
> - The service model for tapestry.persist.ClientPropertyPersistenceStrategy was primitive, not threaded
> - The initialize method was not named properly
> The end result is that a single ClientPropertyPersistenceStrategy instance was being shared between all users, so that changes to state by one user would be seen in later requests by all users.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (TAPESTRY-320) "client" persistent properties are shared between users

JIRA tapestry-dev@jakarta.apache.org
In reply to this post by JIRA tapestry-dev@jakarta.apache.org
     [ http://issues.apache.org/jira/browse/TAPESTRY-320?page=all ]

Howard M. Lewis Ship updated TAPESTRY-320:
------------------------------------------

        Version: 4.0
    Fix Version: 4.0

> "client" persistent properties are shared between users
> -------------------------------------------------------
>
>          Key: TAPESTRY-320
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-320
>      Project: Tapestry
>         Type: Bug
>     Versions: 4.0
>     Reporter: Howard M. Lewis Ship
>     Assignee: Howard M. Lewis Ship
>      Fix For: 4.0

>
> This is caused by a number of factors:
> - The service model for tapestry.persist.ClientPropertyPersistenceStrategy was primitive, not threaded
> - The initialize method was not named properly
> The end result is that a single ClientPropertyPersistenceStrategy instance was being shared between all users, so that changes to state by one user would be seen in later requests by all users.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]