SV: why is hashcode() called on page deserialization?

java.lang.NullPointerException at com.company.project.event.SMSEvent.hashCode(SMSEvent.java:334) This looks a lot like an exception we get in one project as well, where a bean serialized into the DiskPageStore comes back with all properties set to null (including the ones tested for in

RE: why is hashcode() called on page deserialization?

is hashcode() called on page deserialization? java.lang.NullPointerException at com.company.project.event.SMSEvent.hashCode(SMSEvent.java:334) This looks a lot like an exception we get in one project as well, where a bean serialized into the DiskPageStore comes back with all properties set

why is hashcode() called on page deserialization?

Hello, everyone! I get the exception: java.lang.NullPointerException at com.company.project.event.SMSEvent.hashCode(SMSEvent.java:334) at java.util.HashMap.putForCreate(HashMap.java:413) at java.util.HashMap.readObject(HashMap.java:1031) at

Re: why is hashcode() called on page deserialization?

I guess you have a HashMap field in your component, which has an entry with an SMSEvent object as key. You probably shouldn't hold on to references to spring loaded objects. Instead, you should just have an accessor object, which knows how to reload that spring loaded object, e.g.

RE: why is hashcode() called on page deserialization?

@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? I guess you have a HashMap field in your component, which has an entry with an SMSEvent object as key. You probably shouldn't hold on to references to spring loaded objects. Instead, you should just have an accessor object

Re: why is hashcode() called on page deserialization?

is hashcode() called on page deserialization? I guess you have a HashMap field in your component, which has an entry with an SMSEvent object as key. You probably shouldn't hold on to references to spring loaded objects. Instead, you should just have an accessor object, which knows how to reload

RE: why is hashcode() called on page deserialization?

I don't have any HashMap-s that use SMSEvent object as a key. Only List-s Regards, Martin -Original Message- From: Jonas [mailto:barney...@gmail.com] Sent: Friday, March 12, 2010 3:29 PM To: users@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? Yes

Re: why is hashcode() called on page deserialization?

@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? Yes, exactly. But the stacktrace you posted is about a HashMap that is directly referenced from one of your components - you should also use e.g. LoadableDetachableModel there, I guess. On Fri, Mar 12, 2010 at 2:25 PM

RE: why is hashcode() called on page deserialization?

(JIoEndpoint.java:454) at java.lang.Thread.run(Thread.java:619) -Original Message- From: Jonas [mailto:barney...@gmail.com] Sent: Friday, March 12, 2010 3:51 PM To: users@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? Well, the stacktrace you posted is about

Re: why is hashcode() called on page deserialization?

, 2010 3:29 PM To: users@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? Yes, exactly. But the stacktrace you posted is about a HashMap that is directly referenced from one of your components - you should also use e.g. LoadableDetachableModel there, I guess

RE: why is hashcode() called on page deserialization?

Thanks, Jonas, just will try to locate the cache and remove it. Best, Martin -Original Message- From: Jonas [mailto:barney...@gmail.com] Sent: Friday, March 12, 2010 4:56 PM To: users@wicket.apache.org Subject: Re: why is hashcode() called on page deserialization? That's odd - are you