You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Will Glass-Husain (JIRA)" <ji...@apache.org> on 2007/03/14 08:55:09 UTC

[jira] Created: (TRB-41) User/Group/Role and TorqueObject should be serializable

User/Group/Role and TorqueObject should be serializable
-------------------------------------------------------

                 Key: TRB-41
                 URL: https://issues.apache.org/jira/browse/TRB-41
             Project: Turbine
          Issue Type: Bug
    Affects Versions: Core 2.3.2
            Reporter: Will Glass-Husain
         Attachments: serialize.patch

In Turbine 2.3.2, when I shut down/restart Tomcat I'm automatically logged out.  When I restart I get an exception on  value.unbound() from the session.  (I'm using the Torque Security service.)

The problem is that TorqueUser is only partially serialized/deserialized.  Specfically the superclass TorqueObject is not serializable.  The TorqueUser is saved upon shutdown of Tomcat but the persistent object is not.  Thus when Tomcat starts back up the user is not logged in.

I've attached a patch that sets TorqueObject to be serializable.  Also Group, Role, and Permission.  (This parallels User, which is already serializable, and allows the AccessControlObject to be serialized).

I note that Turbine has been extensively restructured for 2.4.  But I'd be interested in seeing this patch be applied to the Turbine 2.3 branch.  Would anyone mind if I applied it?

(I'm a Jakarta and Velocity committer and long-term Turbine user.  I think some of my bug fixes back in 2002 made it into Turbine 2.3, but I've been in stealth mode on the lists since).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Resolved: (TRB-41) User/Group/Role and TorqueObject should be serializable

Posted by "Will Glass-Husain (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TRB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Glass-Husain resolved TRB-41.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Core 2.3.3

Committed - thanks!

> User/Group/Role and TorqueObject should be serializable
> -------------------------------------------------------
>
>                 Key: TRB-41
>                 URL: https://issues.apache.org/jira/browse/TRB-41
>             Project: Turbine
>          Issue Type: Bug
>    Affects Versions: Core 2.3.2
>            Reporter: Will Glass-Husain
>             Fix For: Core 2.3.3
>
>         Attachments: serialize.patch
>
>
> In Turbine 2.3.2, when I shut down/restart Tomcat I'm automatically logged out.  When I restart I get an exception on  value.unbound() from the session.  (I'm using the Torque Security service.)
> The problem is that TorqueUser is only partially serialized/deserialized.  Specfically the superclass TorqueObject is not serializable.  The TorqueUser is saved upon shutdown of Tomcat but the persistent object is not.  Thus when Tomcat starts back up the user is not logged in.
> I've attached a patch that sets TorqueObject to be serializable.  Also Group, Role, and Permission.  (This parallels User, which is already serializable, and allows the AccessControlObject to be serialized).
> I note that Turbine has been extensively restructured for 2.4.  But I'd be interested in seeing this patch be applied to the Turbine 2.3 branch.  Would anyone mind if I applied it?
> (I'm a Jakarta and Velocity committer and long-term Turbine user.  I think some of my bug fixes back in 2002 made it into Turbine 2.3, but I've been in stealth mode on the lists since).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (TRB-41) User/Group/Role and TorqueObject should be serializable

Posted by "Will Glass-Husain (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TRB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Glass-Husain updated TRB-41:
---------------------------------

    Attachment: serialize.patch

> User/Group/Role and TorqueObject should be serializable
> -------------------------------------------------------
>
>                 Key: TRB-41
>                 URL: https://issues.apache.org/jira/browse/TRB-41
>             Project: Turbine
>          Issue Type: Bug
>    Affects Versions: Core 2.3.2
>            Reporter: Will Glass-Husain
>         Attachments: serialize.patch
>
>
> In Turbine 2.3.2, when I shut down/restart Tomcat I'm automatically logged out.  When I restart I get an exception on  value.unbound() from the session.  (I'm using the Torque Security service.)
> The problem is that TorqueUser is only partially serialized/deserialized.  Specfically the superclass TorqueObject is not serializable.  The TorqueUser is saved upon shutdown of Tomcat but the persistent object is not.  Thus when Tomcat starts back up the user is not logged in.
> I've attached a patch that sets TorqueObject to be serializable.  Also Group, Role, and Permission.  (This parallels User, which is already serializable, and allows the AccessControlObject to be serialized).
> I note that Turbine has been extensively restructured for 2.4.  But I'd be interested in seeing this patch be applied to the Turbine 2.3 branch.  Would anyone mind if I applied it?
> (I'm a Jakarta and Velocity committer and long-term Turbine user.  I think some of my bug fixes back in 2002 made it into Turbine 2.3, but I've been in stealth mode on the lists since).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Commented: (TRB-41) User/Group/Role and TorqueObject should be serializable

Posted by "Scott Eade (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TRB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480734 ] 

Scott Eade commented on TRB-41:
-------------------------------

I don't have any problem with you committing this to the 2.3 branch (nor TRB-42) and I doubt that any of the others involved will either.  Please go ahead and do so.

Scott

> User/Group/Role and TorqueObject should be serializable
> -------------------------------------------------------
>
>                 Key: TRB-41
>                 URL: https://issues.apache.org/jira/browse/TRB-41
>             Project: Turbine
>          Issue Type: Bug
>    Affects Versions: Core 2.3.2
>            Reporter: Will Glass-Husain
>         Attachments: serialize.patch
>
>
> In Turbine 2.3.2, when I shut down/restart Tomcat I'm automatically logged out.  When I restart I get an exception on  value.unbound() from the session.  (I'm using the Torque Security service.)
> The problem is that TorqueUser is only partially serialized/deserialized.  Specfically the superclass TorqueObject is not serializable.  The TorqueUser is saved upon shutdown of Tomcat but the persistent object is not.  Thus when Tomcat starts back up the user is not logged in.
> I've attached a patch that sets TorqueObject to be serializable.  Also Group, Role, and Permission.  (This parallels User, which is already serializable, and allows the AccessControlObject to be serialized).
> I note that Turbine has been extensively restructured for 2.4.  But I'd be interested in seeing this patch be applied to the Turbine 2.3 branch.  Would anyone mind if I applied it?
> (I'm a Jakarta and Velocity committer and long-term Turbine user.  I think some of my bug fixes back in 2002 made it into Turbine 2.3, but I've been in stealth mode on the lists since).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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