Components not reloading on url change in Wicket 1.5(.2)?

Question

I navigate to my application the first time with following URL:

.../homepage/?0&user=x

In debug mode I see wicket is nicely instantiating my panels and such (obviously).

if I change the URL to:

.../homepage/?0&user=y

then nothing happens, the panels are not re-initialized (for the new user => data of user x is still shown) nor are LoadableDetachable -or other models invoked.

However, if I change the URL to:

.../homepage/?1&user=y

then all panels are nicely initialized for user y

One step further, if you change the URL back to

.../homepage/?0&user=y

then again the data for user x is displayed.

It seems that Wicket does not care that arguments have changed in the URL to decide whether or not to reload components. AFAIK this was working fine in Wicket 1.4. I think I understand the logic behind this behavior but am not sure. Also, I would like to know how to force Wicket to reload if custom parameters change and how to remove that 'ugly' ?0 from the URL (if possible)?

I can reproduce this behavior with my own application. The RequestLogger prints out a new request with the old pageID but with the changed PageParameter. I guess this behavior is intended as you still request the same old pageID. However I'm also interested in removing the ugly pageID from the url... — rotsch, Nov 10 '11 at 15:00
Tried out deploying my app as "deployment"-build, still got the pageIDs. Thought that would be for development only. — rotsch, Nov 10 '11 at 15:11
@Rotsch thanks for trying out; I had not thought of that myself yet. — Stijn Geukens, Nov 10 '11 at 15:13
Just noticed something in AbstractBookmarkableMapper.mapRequest: if there is a pageId (?0) then it will call processHybrid, the javadoc mentions: 'if there is page instance information in the URL we need to try to reuse existing page instance. — Stijn Geukens, Nov 10 '11 at 15:23

score 5 · Accepted Answer · answered Nov 10 '11 at 15:34

5

This is the stateful nature of Wicket. The page is instantiated once, the parameters are parsed and so on. Later you pass different parameters to the already instantiated page but this time its constructor is not called at all and thus PageParameters are not updated. Changing to ?1 asks Wicket for page with id 1 and since there is no such Wicket instantiates a new instance and passes the new parameters. If you want to always have the latest request parameters then use getRequest().getRequestParameter("user") which will give you what you need. Makes sense ?

answered Nov 10 '11 at 15:34

martin-g

17,243
2
23
35

Makes sense but where should I call getRequest().getRequestParameter("user") if Wicket is not calling my constructor at all? – Stijn Geukens Nov 10 '11 at 15:38
1

I kind of dislike the new pageIDs in Bookmarkable pages as well, for the end user, the way wicket 1.4 behaved was more logical. – bert Nov 10 '11 at 21:41
@TheStijn: onConfigure()/onBeforeRender(). – martin-g Nov 13 '11 at 17:02
@bert: it is as with HybridUrlCodingStrategy in 1.4 – martin-g Nov 13 '11 at 17:03
@Martin-g; tx, I'll try this out. – Stijn Geukens Nov 13 '11 at 17:20

score 2 · Answer 2 · answered Nov 13 '11 at 08:36

To amend martin-g's answer: you should retrieve the request parameter in your model, and retrieve the correct user with the request parameter. Something like:

setModel(new LoadableDetachableModel<User>(){
    public User load() {
        String username = getRequest().getRequestParameter("user");
        return userservice.byUsername(username);
    }
}));

When you need dynamic data, almost always use models to solve your problem.

score 0 · Answer 3 · edited Aug 01 '18 at 16:09

0

I think you can use onRender or onConfigure

edited Aug 01 '18 at 16:09

gtgaxiola

9,241
5
42
64

answered Mar 28 '13 at 08:50

Rudi Wijaya

872
1
10
25

Components not reloading on url change in Wicket 1.5(.2)?

3 Answers3

Linked