title: Components not reloading on url change in Wicket 1.5(.2)?
body: <p>I navigate to my application the first time with following URL:</p>
  
  <blockquote>
    <p>.../homepage/?0&amp;user=<strong>x</strong></p>
  </blockquote>
  
  <p>In debug mode I see wicket is nicely instantiating my panels and such (obviously).</p>
  
  <p>if I change the URL to:</p>
  
  <blockquote>
    <p>.../homepage/?0&amp;user=<strong>y</strong></p>
  </blockquote>
  
  <p>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.</p>
  
  <p>However, if I change the URL to:</p>
  
  <blockquote>
    <p>.../homepage/?<strong>1</strong>&amp;user=y</p>
  </blockquote>
  
  <p>then all panels are nicely initialized for user <strong>y</strong></p>
  
  <p>One step further, if you change the URL back to</p>
  
  <blockquote>
    <p>.../homepage/?<strong>0</strong>&amp;user=<strong>y</strong></p>
  </blockquote>
  
  <p>then again the data for user <strong>x</strong> is displayed.</p>
  
  <p>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)?</p>