On 12/1/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> your models shouldnt keep a reference to that object, they should know how
> to retrieve it and do so when getobject() is called.
i.e. in your case:
class MyFinanModel extends Model {
public Object getObject(Component component) {
s to give it to the method
directly. So I hope that's not where the problem is.
Regards,
Arjan Zwaan.
Date: Thu, 30 Nov 2006 15:05:30 +0100
From: Erik van Oosten <[EMAIL PROTECTED]>
Subject: Re: [Wicket-user] Problem disabling PageMaps (Erik van
Oosten)
To: wicke
;[EMAIL PROTECTED]>
Subject: Re: [Wicket-user] Problem disabling PageMaps (Erik van
Oosten)
To: wicket-user@lists.sourceforge.net
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Arjan,
What Wicket version are you using?
Hi Arjan,
What Wicket version are you using?
In addition, you can try to identify components that keep references to
objects outside the page structure. In wicket 2 this will all be
serialized so you need to keep your components lean. If you use
clustering this is also important in wicket 1.
Hello Erik,
We are running in deployment mode, I'm afraid we already tried that.
It seems to be the PageMaps that are causing the problems by writing a
lot of data to an outputstream. Also having multiple PageMaps is
unnecessary in our case, but the Application seems to keep making new
ones. I
