Re: WOSession serialisation redux
Re: WOSession serialisation redux
- Subject: Re: WOSession serialisation redux
- From: Paul Hoadley <email@hidden>
- Date: Thu, 21 May 2015 11:15:18 +0930
On 20 May 2015, at 9:21 am, Paul Hoadley <email@hidden> wrote:
> On 20 May 2015, at 1:53 am, Ramsey Gurley <email@hidden> wrote:
>
>> On May 19, 2015, at 4:03 AM, Paul Hoadley <email@hidden> wrote:
>>
>>> I’ve had a look at Ramsey’s ERPersistentSessionStorage.framework, and my intention was to create something similar backed by memcached. I got it working to the proof-of-concept level on a trivial app, but using native Java serialisation seems brittle. (By which I mean it falls over pretty fast when you throw a serialisation-based approach into a substantial application.)
>>
>> I’m curious about the "falls over pretty fast" part. What sort of problems do you have?
>
> Serialization failures. (To be clear, I’m talking about testing with my own memcached-based approach, but it’s really only some very minor changes to your work to use memcached instead of the database as the back-end.) Initially it was my own classes, which I could fix, but then I started hitting weirdness like this:
>
>> Caused by: java.io.NotSerializableException: java.lang.reflect.Field
>
> It’s not obvious to me where that’s coming from, or how to fix it.
Having just discovered this:
-Dsun.io.serialization.extendedDebugInfo=true
I can report that the java.lang.reflect.Field is in an ERXDisplayGroup. And here it is:
> public class ERXDisplayGroup<T> extends WODisplayGroup {
> private Field displayedObjectsField;
So is ERXDisplayGroup simply not serializable, and hence I’d need to pull it from any application that wanted to use ERPersistentSessionStorage.framework?
--
Paul Hoadley
http://logicsquad.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden