Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-05 Thread Johan Compagner
the first time path=0 is shown yes The second time path=1 is shown Then i restart the tomcat server, let tomcat store my sessions then i go again to that page. Tomcat picks up my stored session and starts counting from 2 so the first time after a restart path=2. If ofcourse you completely close

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-05 Thread Matej Knopp
Hi I think it would be nice to have a feature in 1.2 that would allow having single instance of certain pages. For example if I said that MyPage class is singleton, bookmarkablePage=MyPage would search the PageMap if there is any instance of MyPage and if it's there, it would use it. Another

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-05 Thread Matej Knopp
Matej Knopp wrote: Hi I think it would be nice to have a feature in 1.2 that would allow having single instance of certain pages. For example if I said that MyPage class is singleton, bookmarkablePage=MyPage would search the PageMap if there is any instance of MyPage and if it's there, it

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-05 Thread Johan Compagner
don't cache non static images then. so that images with path will always be asked for On 10/5/05, Gili [EMAIL PROTECTED] wrote: Maybe that's it... If one restarts the browser and you get path=0again, the browser still expects the same URLs to yield the same imagesbut this might not be

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-05 Thread Gili
So I would say something is fundamentally mismatched between what I am trying to tell Wicket to do and what it is actually doing (i.e. a RFE of some sort). I expect my bookmarkable pages to have fixed URLs so that the browser can cache the images contained therein for one day. I would say

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-04 Thread Johan Compagner
not at my place. Just tested it by running examples (forminput) on my tomcat install. Did go a few times to the forminput page so that the path=3 was showing as last shutdown tomcat. Started it again. Then did go to the forminput page again and the path=4 was there. On 10/4/05, Gili [EMAIL

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-04 Thread Michael Jouravlev
The path counter issue is a result of creating several instances of one component, usually a Page. I asked about possibility of having only one instanse of a Page, for different reason then this one. Still, having only one instance of certain entry pages would solve the problem. Do bookmarkable

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-04 Thread Johan Compagner
as i said before in some post: if you want to have one instance of a page then hold that one in youre wicket session and take that one. you can hold references to page objects however you like. bookmarkable pages (bookmarkable urls is a better name) have there stabe url yes from that point on

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-04 Thread Gili
My application is 100% bookmarkable pages. Is FormInput one? Also, when I hit FormInput on wicket-library.com it was at path=0 so I don't see how this could have worked for you (because it is unlikely we'd be at path=0 at this point). Something doesn't sound right here. There must be a

RE: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-04 Thread Igor Vaynberg
Also, when I hit FormInput on wicket-library.com it was at path=0 so I don't see how this could have worked for you (because it is unlikely we'd be at path=0 at this point). path=0 is session relative. It depicts the name of the page in the user's session. -Igor

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Gili
Even if the images are dynamically generated, couldn't we serialize the highest path value used on shutdown and reuse it on startup? Consider the following use-case: - Images are dynamically generated from a DB - Expiration headers are set to cache the images for one day on the client end

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Eelco Hillenius
I think you can do that if you want to. Packaged resources don't have to be static afaik, but could be generated as well. Eelco On 10/3/05, Gili [EMAIL PROTECTED] wrote: Even if the images are dynamically generated, couldn't we serialize the highest path value used on shutdown and

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Johan Compagner
Server restart should work All sessions are serialized to disk and read back in. On 10/3/05, Gili [EMAIL PROTECTED] wrote: Even if the images are dynamically generated, couldn't we serialize thehighest path value used on shutdown and reuse it on startup? Considerthe following use-case:- Images are

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Eelco Hillenius
... when you work with Tomcat... On 10/3/05, Johan Compagner [EMAIL PROTECTED] wrote: Server restart should work All sessions are serialized to disk and read back in. On 10/3/05, Gili [EMAIL PROTECTED] wrote: Even if the images are dynamically generated, couldn't we serialize

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Johan Compagner
all application servers shoujld work that way. Only you have to terminate them the right way really shutdown them like the want to. On 10/3/05, Eelco Hillenius [EMAIL PROTECTED] wrote: ... when you work with Tomcat...On 10/3/05, Johan Compagner [EMAIL PROTECTED] wrote: Server restart should

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Eelco Hillenius
What they want != what I want: immediate kill! :) But app servers aren't obliged to store session info on shut down by any spec or convention are they? Eelco On 10/3/05, Johan Compagner [EMAIL PROTECTED] wrote: all application servers shoujld work that way. Only you have to terminate them the

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-03 Thread Gili
That might be so, but practically speaking this doesn't occur. Try this yourself and you will notice that path is always reset to a value of one on every server restart. For an unknown reason, it is not resumed on restart. Can someone investigate this? Gili Johan Compagner wrote: Server

Re: [Wicket-user] Browser cache doesn't like Wicket path

2005-10-02 Thread Eelco Hillenius
That's why we introduced packaged resources in the first place: to have static urls. If you don't have static urls, your browser shouldn't cache them. Don't we set expiry headers? Eelco On 10/1/05, Gili [EMAIL PROTECTED] wrote: Hi, I'm using PageableGridDataView to display a grid of