Re: [Wicket-user] Problem disabling PageMaps (Erik van Oosten)
Hello Erik, I'm using wicket 1.2. The pages themselves get the data from an object in the session every time it's needed. There are quite a few panels though that use models which in turn do have a reference to the object in the session. But I don't see a possibility of changing that somehow, the models need access to the object in several methods, and I can't use parameters 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: 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? 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. Erik. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Problem disabling PageMaps (Erik van Oosten)
your models shouldnt keep a reference to that object, they should know how to retrieve it and do so when getobject() is called. -igor On 12/1/06, A. Zwaan [EMAIL PROTECTED] wrote: Hello Erik, I'm using wicket 1.2. The pages themselves get the data from an object in the session every time it's needed. There are quite a few panels though that use models which in turn do have a reference to the object in the session. But I don't see a possibility of changing that somehow, the models need access to the object in several methods, and I can't use parameters 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: 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? 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. Erik. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Problem disabling PageMaps (Erik van Oosten)
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) {
return FinanSession.get().getMyFinanObject();
}
public void setObject(Object object, Component component) {
return FinanSession.get().setMyFinanObject(object);
}
}
Martijn
--
a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a
for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a
at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in
the World!/a
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Problem disabling PageMaps (Erik van Oosten)
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. Erik. A. Zwaan schreef: 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 have tried various settings for PageMaps, but none of them seem to work. The settings I tried were: - getApplication().getPageSettings().setMaxPageVersions(0); - getApplication().getPageSettings().setVersionPagesByDefault(false); - getApplication().getSessionSettings().setMaxPageMaps(1); Regards, Arjan Zwaan. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
