Re: Accessing PageParameters within Panel

2015-03-12 Thread Tobias Soloschenko 
Hi,

https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5

Search for Request parameters

kind regards

Tobias

 Am 12.03.2015 um 17:20 schrieb David Kaufman david.kauf...@gmx.de:
 
 Hi,
 
 I'm currently migrating a fairly large project from wicket 1.4 to wicket 6.
 
 We're currently getting the PageParameters from the RequestCycle
 via getRequestCycle().getPageParameters(), with wicket 6 this is no longer
 possible. Getting the PageParameters via getPage().getPageParameters() is a
 viable option but I'm not quite sure if this is the way to go. Another way
 of getting parameters is by calling getRequest().getQueryParameters() but
 I'm also not sure if these are identical with the PageParameters (they are
 differently typed so I suspect that they are inherently different).
 
 Thanks,
 David

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Accessing PageParameters within Panel

2015-03-12 Thread Martin Grigorov 
Hi,

getPage().getPageParameters() returns the GET parameters at the time the
page has been created.
If the page is stateful and you submit a form, or click a link (normal and
Ajax ones) then you need getRequest().get***Parameters().

Martin Grigorov
Freelancer, available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Mar 12, 2015 at 6:20 PM, David Kaufman david.kauf...@gmx.de wrote:

 Hi,

 I'm currently migrating a fairly large project from wicket 1.4 to wicket 6.

 We're currently getting the PageParameters from the RequestCycle
 via getRequestCycle().getPageParameters(), with wicket 6 this is no longer
 possible. Getting the PageParameters via getPage().getPageParameters() is a
 viable option but I'm not quite sure if this is the way to go. Another way
 of getting parameters is by calling getRequest().getQueryParameters() but
 I'm also not sure if these are identical with the PageParameters (they are
 differently typed so I suspect that they are inherently different).

 Thanks,
 David