You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Siegfried Goeschl <si...@it20one.at> on 2007/11/05 22:33:57 UTC
[VOTE RESULT] fulcrum-crypto-1.0.6 release
Hi folks,
here is the result of the vote for releasing fulcrum-crypto-1.0.6
Binding Votes
+1 Siegfried Goeschl
+1 Scott Eade
+1 Thomas Vandahl
Cheers,
Siegfried Goeschl
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
RE: TorqueUser loses persistent object during session replication
Posted by Declan Shanaghy <tu...@shanaghy.com>.
Wait a second, scratch that.
The tempStorage, permStorage and lastAccessTime
are all being serialized successfully so my workaround
is valid.
It is the TorqueObject.obj (declared as type
org.apache.torque.om.Persistent)
that is not being serialized correctly.
Its real implementation derives from org.apache.torque.om.BaseObject which
is also serializable.
All the classes in my chain are serializable (otherwise i would see
NotSerializableException
(like i posted on the dev list). Its just that data thats being lost.
-----Original Message-----
From: Declan Shanaghy [mailto:turbine@shanaghy.com]
Sent: Tuesday, December 04, 2007 4:41 PM
To: 'Turbine Users List'
Subject: RE: TorqueUser loses persistent object during session replication
I had a sneaking suspicion that subclassing TorqueUser
and marking it serializable would not work
Do fields of the parent objects in a hierarchy not get serialized
when a subclass is marked serializable?
-----Original Message-----
From: Will Glass-Husain [mailto:wglasshusain@gmail.com]
Sent: Tuesday, December 04, 2007 8:53 AM
To: Turbine Users List
Subject: Re: TorqueUser loses persistent object during session replication
Hi Declan,
I think TorqueUser is not serializable. I corrected this in the svn for the
2.3x branch. I'm using svn head for that branch, it seems pretty stable.
https://issues.apache.org/jira/browse/TRB-41
WILL
On Dec 3, 2007 1:24 PM, Declan Shanaghy <tu...@shanaghy.com> wrote:
> Hello list,
> I'm having a slight problem with TorqueUser
> session replication in my turbine 2.3.1 app.
>
> When the session is replicated the underlying
> persistent object in TorqueUser is lost.
>
> The tempStorage, permStorage and lastAccessDate
> fields are all valid but the persistent object is
> null, upon first access it is initialized to its
> default value which is an empty object.
>
> This causes my app to fail because it is being told the user is
> logged in when hasLoggedIn() returns true but the returned user object is
> empty.
>
> I have been able to workaround by checking for
> user.hasLoggedIn() == true && user.getName() == null
> and then reload the TorqueUser into the runData object
> just as if the user was logging into the app
> but I'd prefer to find a real solution than have to work around this.
>
>
> The Persistent object and all of its fields are not transient so
> the data should be replicated just like everything else?
>
> Does anyone have any idea why this is happening?
>
>
>
> Cheers,
> Declan Shanaghy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
RE: TorqueUser loses persistent object during session replication
Posted by Declan Shanaghy <tu...@shanaghy.com>.
I had a sneaking suspicion that subclassing TorqueUser
and marking it serializable would not work
Do fields of the parent objects in a hierarchy not get serialized
when a subclass is marked serializable?
-----Original Message-----
From: Will Glass-Husain [mailto:wglasshusain@gmail.com]
Sent: Tuesday, December 04, 2007 8:53 AM
To: Turbine Users List
Subject: Re: TorqueUser loses persistent object during session replication
Hi Declan,
I think TorqueUser is not serializable. I corrected this in the svn for the
2.3x branch. I'm using svn head for that branch, it seems pretty stable.
https://issues.apache.org/jira/browse/TRB-41
WILL
On Dec 3, 2007 1:24 PM, Declan Shanaghy <tu...@shanaghy.com> wrote:
> Hello list,
> I'm having a slight problem with TorqueUser
> session replication in my turbine 2.3.1 app.
>
> When the session is replicated the underlying
> persistent object in TorqueUser is lost.
>
> The tempStorage, permStorage and lastAccessDate
> fields are all valid but the persistent object is
> null, upon first access it is initialized to its
> default value which is an empty object.
>
> This causes my app to fail because it is being told the user is
> logged in when hasLoggedIn() returns true but the returned user object is
> empty.
>
> I have been able to workaround by checking for
> user.hasLoggedIn() == true && user.getName() == null
> and then reload the TorqueUser into the runData object
> just as if the user was logging into the app
> but I'd prefer to find a real solution than have to work around this.
>
>
> The Persistent object and all of its fields are not transient so
> the data should be replicated just like everything else?
>
> Does anyone have any idea why this is happening?
>
>
>
> Cheers,
> Declan Shanaghy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
Re: TorqueUser loses persistent object during session replication
Posted by Will Glass-Husain <wg...@gmail.com>.
Hi Declan,
I think TorqueUser is not serializable. I corrected this in the svn for the
2.3x branch. I'm using svn head for that branch, it seems pretty stable.
https://issues.apache.org/jira/browse/TRB-41
WILL
On Dec 3, 2007 1:24 PM, Declan Shanaghy <tu...@shanaghy.com> wrote:
> Hello list,
> I'm having a slight problem with TorqueUser
> session replication in my turbine 2.3.1 app.
>
> When the session is replicated the underlying
> persistent object in TorqueUser is lost.
>
> The tempStorage, permStorage and lastAccessDate
> fields are all valid but the persistent object is
> null, upon first access it is initialized to its
> default value which is an empty object.
>
> This causes my app to fail because it is being told the user is
> logged in when hasLoggedIn() returns true but the returned user object is
> empty.
>
> I have been able to workaround by checking for
> user.hasLoggedIn() == true && user.getName() == null
> and then reload the TorqueUser into the runData object
> just as if the user was logging into the app
> but I'd prefer to find a real solution than have to work around this.
>
>
> The Persistent object and all of its fields are not transient so
> the data should be replicated just like everything else?
>
> Does anyone have any idea why this is happening?
>
>
>
> Cheers,
> Declan Shanaghy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
TorqueUser loses persistent object during session replication
Posted by Declan Shanaghy <tu...@shanaghy.com>.
Hello list,
I'm having a slight problem with TorqueUser
session replication in my turbine 2.3.1 app.
When the session is replicated the underlying
persistent object in TorqueUser is lost.
The tempStorage, permStorage and lastAccessDate
fields are all valid but the persistent object is
null, upon first access it is initialized to its
default value which is an empty object.
This causes my app to fail because it is being told the user is
logged in when hasLoggedIn() returns true but the returned user object is
empty.
I have been able to workaround by checking for
user.hasLoggedIn() == true && user.getName() == null
and then reload the TorqueUser into the runData object
just as if the user was logging into the app
but I'd prefer to find a real solution than have to work around this.
The Persistent object and all of its fields are not transient so
the data should be replicated just like everything else?
Does anyone have any idea why this is happening?
Cheers,
Declan Shanaghy
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
RE: TorqueSecurity service classes
Posted by Declan Shanaghy <tu...@shanaghy.com>.
OK thanks,
Im still running off the 2.3.1 release version
so the workaround will suffice for now.
-----Original Message-----
From: Will Glass-Husain [mailto:wglasshusain@gmail.com]
Sent: Tuesday, November 20, 2007 7:30 AM
To: Turbine Developers List
Subject: Re: TorqueSecurity service classes
Hi Declan,
I hit the same issue and submitted/committed a patch to svn (2.3 branch).
I'm running from svn head for the 2.3 branch - works fine.
WILL
On Nov 20, 2007 12:14 AM, Declan Shanaghy <tu...@shanaghy.com> wrote:
>
> I'm setting up a 2 node tomcat cluster running
> my app which is based on Turbine 2.3.1
>
> I was having a problem with session serialization and managed to
> pin it down to Turbine placing its access control list in the session.
> The access control list contained the default TorqueSecurity classes
> which are as follows
>
> org.apache.turbine.services.security.torque.TorqueUser
> org.apache.turbine.services.security.torque.TorqueRole
> org.apache.turbine.services.security.torque.TorquePermission
> org.apache.turbine.services.security.torque.TorqueGroup
>
> None of these classes implement java.io.Serializable, hence session
> serialization between nodes always fails with a NotSerializableException.
>
> I was able to overcome the problem by subclassing these classes and
> adding the Serilization marker interface.
>
>
> But i am wondering is this by design or is it a bug, and if it
> is a concious design decision then why?
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: TorqueSecurity service classes
Posted by Will Glass-Husain <wg...@gmail.com>.
Hi Declan,
I hit the same issue and submitted/committed a patch to svn (2.3 branch).
I'm running from svn head for the 2.3 branch - works fine.
WILL
On Nov 20, 2007 12:14 AM, Declan Shanaghy <tu...@shanaghy.com> wrote:
>
> I'm setting up a 2 node tomcat cluster running
> my app which is based on Turbine 2.3.1
>
> I was having a problem with session serialization and managed to
> pin it down to Turbine placing its access control list in the session.
> The access control list contained the default TorqueSecurity classes
> which are as follows
>
> org.apache.turbine.services.security.torque.TorqueUser
> org.apache.turbine.services.security.torque.TorqueRole
> org.apache.turbine.services.security.torque.TorquePermission
> org.apache.turbine.services.security.torque.TorqueGroup
>
> None of these classes implement java.io.Serializable, hence session
> serialization between nodes always fails with a NotSerializableException.
>
> I was able to overcome the problem by subclassing these classes and
> adding the Serilization marker interface.
>
>
> But i am wondering is this by design or is it a bug, and if it
> is a concious design decision then why?
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
TorqueSecurity service classes
Posted by Declan Shanaghy <tu...@shanaghy.com>.
I'm setting up a 2 node tomcat cluster running
my app which is based on Turbine 2.3.1
I was having a problem with session serialization and managed to
pin it down to Turbine placing its access control list in the session.
The access control list contained the default TorqueSecurity classes
which are as follows
org.apache.turbine.services.security.torque.TorqueUser
org.apache.turbine.services.security.torque.TorqueRole
org.apache.turbine.services.security.torque.TorquePermission
org.apache.turbine.services.security.torque.TorqueGroup
None of these classes implement java.io.Serializable, hence session
serialization between nodes always fails with a NotSerializableException.
I was able to overcome the problem by subclassing these classes and
adding the Serilization marker interface.
But i am wondering is this by design or is it a bug, and if it
is a concious design decision then why?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org