The issue is that the object that hashCode() is called on contains a @Lob
object, I think it has to do with it...
Regards,
-Original Message-
From: Wilhelmsen Tor Iver [mailto:toriv...@arrive.no]
Sent: Monday, March 15, 2010 10:01 AM
To: users@wicket.apache.org
Subject: SV: why is hashc
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 - ar
e.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
> at
> org.apache.coyote.http11.Http11Protocol$H
Worker.run(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 poste
0 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. LoadableDetachable
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?
with List passed as an argument. You
> mean to replace the List with LoadableDetachableModel, that returns the List?
>
> Regards,
>
> -Original Message-
> From: Jonas [mailto:barney...@gmail.com]
> Sent: Friday, March 12, 2010 3:18 PM
> To: users@wicket.apache.o
@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,
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. LoadableDetachabl
