You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@wicket.apache.org by Adib Saikali <ad...@programmingmastery.com> on 2008/08/01 05:52:14 UTC

RequestParamters vs. PageParameters

Hi,

What is the key distinction between RequestParameters and PageParamters why
are two classes needed? 

Thakns
Adib

Re: RequestParamters vs. PageParameters

Posted by ig...@gmail.com.

requestparams are wicket's internal representation. Pageparams are
userspace and only contain user-relevant params.

-Igor

On 8/1/08, Martin Grigorov <mc...@e-card.bg> wrote:
> On Thu, 2008-07-31 at 20:52 -0700, Adib Saikali wrote:
>> Hi,
>>
>> What is the key distinction between RequestParameters and PageParamters
>> why
>> are two classes needed?
>>
>> Thakns
>> Adib
>>
>>
> PageParameters is OO representation of the query string. It provides
> convenient methods like ".getInteger('paramName')".
>
> RequestParameters is Wicket internal class where are saved the
> componentPath, version, pageMapName, ... All of these are used mostly by
> the framework.
>
> Both of these classes have javadocs. If you think they could be improved
> then create a ticket in the Jira and attach a patch.
>
>

Re: RequestParamters vs. PageParameters

Posted by Martin Grigorov <mc...@e-card.bg>.

On Thu, 2008-07-31 at 20:52 -0700, Adib Saikali wrote:
> Hi,
> 
> What is the key distinction between RequestParameters and PageParamters why
> are two classes needed? 
> 
> Thakns
> Adib
> 
> 
PageParameters is OO representation of the query string. It provides
convenient methods like ".getInteger('paramName')".

RequestParameters is Wicket internal class where are saved the
componentPath, version, pageMapName, ... All of these are used mostly by
the framework.

Both of these classes have javadocs. If you think they could be improved
then create a ticket in the Jira and attach a patch.