Thank you very much Jeremy! It was a good read through, very informative! I already browsed through Ivan's post but deemed it unrelevant to my problem on the first read. After reading the second post, then reading Ivan's post again, I now understand the page versioning system a lot better :)
Sadly though now I'm not sure there is a solution to my problem and that I will have to cope with how the versioning/url works now. I'm looking for another way to encode the page version, possibly not into the url but using cookies/http headers/session/anything. I will search nabble/stackoverflow for this. If you already have links to posts dealing with this matter feel free to post them :) I will definitely post any links I find that are useful for anyone who encounters this post in the future. On Thu, Jul 12, 2012 at 2:43 AM, Jeremy Thomerson <[email protected] > wrote: > On Wed, Jul 11, 2012 at 6:41 PM, Jeremy Thomerson < > [email protected] > > wrote: > > > > > On Wed, Jul 11, 2012 at 2:54 PM, Sam Zilverberg <[email protected] > >wrote: > > > >> I have no problem that the page is being constructed everytime. > >> > > > > Just one note here: the page is not being constructed every time. Put a > > breakpoint or System.out.println in your constructor to verify this. > There > > was a change in Wicket 1.5 that increases the page ID for each change > > rather than having the older ID and version number combination. > > > > See this post where Igor schooled me in the new stuff :) > > http://tinyurl.com/cmfrpj9 > > > > -- > > Jeremy Thomerson > > http://wickettraining.com > > *Need a CMS for Wicket? Use Brix! http://brixcms.org* > > > > And see this post for the more direct answer to your original question: > http://tinyurl.com/cdl99xy > > -- > Jeremy Thomerson > http://wickettraining.com > *Need a CMS for Wicket? Use Brix! http://brixcms.org* >
