Re: [Wicket-user] newbie model update question

[Igor Vaynberg]

you should put that computation directly into your model, or write a wrapper for your model that caches the data until its valid. one of the great things about models is that its easy to write decorators and chain them.

-Igor

On 2/1/06, Frank Silbermann <[EMAIL PROTECTED]> wrote:

In Servlet technology we have the concept of request scope, page scope and session scope.  I would assume that Wicket object attributes all go into session scope so that it's still there when a page is posted back – is that correct?

 

Suppose I have an application in which users can go from page 1 to page 2 and back again.  There is some hard-to-compute model data in Page 1 that needs re-computation _only_ if certain application-scope data was changed while the user was on page 2.  I don't want to re-compute the model if the user never returns to page 1, nor if he returns to page 1 and the application-scoped variable has the same value as before.

 

Where in page 1 should I put the code to check the application-scope data for changes and perhaps update the model data?  What Wicket Page method should I override?

 

/Frank Silbermann