You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Nelson Segura <ns...@gmail.com> on 2012/09/18 00:07:43 UTC
PageReference as page parameter?
Hello,
I have a very common pattern in which from a list, I can to detail of
an element in the list.
In the detail page I have a reference back to the page list.
The page list can be different, several list might point to the same detail.
Until now I have been using page reference to return to the previous
page, and it works well.
However, passing the page reference to the constructor of the detail
page, means that page is not bookmarkable (unless I am mistaking
something)
Is there a way a can pass the page reference as a request parameter,
and so make the page bookmarkable? (ex. by using id, page map, etc).
Of course if no page reference can be retraced from the map, then we
just ignore the back reference.
Any ideas?
- Nelson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageReference as page parameter?
Posted by Igor Vaynberg <ig...@gmail.com>.
its public in 6. but yeah, you can do that yourself.
-igor
On Mon, Sep 17, 2012 at 3:20 PM, Nelson Segura <ns...@gmail.com> wrote:
> That is what I thought, but PageReference constructor is not public,
> so I cannot do that, unless I am missing something?
> But I could do
>
> (Page)Session.get().getPageManager().getPage(pageId)
>
> As PageReference does internally, correct?
>
> - Nelson
>
> On Mon, Sep 17, 2012 at 3:11 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>> you can pass in the page id obtained from page#getpageid() as a
>> bookmarkable url, then to navigate back to the original page you can
>> do setResponsePage(new PageReference(pageid).getPage())
>>
>> this will, however, leave you on a nonbookmarkable url when you come back.
>>
>> if you want bookmarkable urls all the way around then you need to do
>> what stateless frameworks do, pass the return url to the detail page
>> as a parameter.
>>
>> -igor
>>
>> On Mon, Sep 17, 2012 at 3:07 PM, Nelson Segura <ns...@gmail.com> wrote:
>>> Hello,
>>> I have a very common pattern in which from a list, I can to detail of
>>> an element in the list.
>>> In the detail page I have a reference back to the page list.
>>> The page list can be different, several list might point to the same detail.
>>> Until now I have been using page reference to return to the previous
>>> page, and it works well.
>>> However, passing the page reference to the constructor of the detail
>>> page, means that page is not bookmarkable (unless I am mistaking
>>> something)
>>>
>>> Is there a way a can pass the page reference as a request parameter,
>>> and so make the page bookmarkable? (ex. by using id, page map, etc).
>>> Of course if no page reference can be retraced from the map, then we
>>> just ignore the back reference.
>>>
>>> Any ideas?
>>>
>>> - Nelson
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageReference as page parameter?
Posted by Nelson Segura <ns...@gmail.com>.
That is what I thought, but PageReference constructor is not public,
so I cannot do that, unless I am missing something?
But I could do
(Page)Session.get().getPageManager().getPage(pageId)
As PageReference does internally, correct?
- Nelson
On Mon, Sep 17, 2012 at 3:11 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> you can pass in the page id obtained from page#getpageid() as a
> bookmarkable url, then to navigate back to the original page you can
> do setResponsePage(new PageReference(pageid).getPage())
>
> this will, however, leave you on a nonbookmarkable url when you come back.
>
> if you want bookmarkable urls all the way around then you need to do
> what stateless frameworks do, pass the return url to the detail page
> as a parameter.
>
> -igor
>
> On Mon, Sep 17, 2012 at 3:07 PM, Nelson Segura <ns...@gmail.com> wrote:
>> Hello,
>> I have a very common pattern in which from a list, I can to detail of
>> an element in the list.
>> In the detail page I have a reference back to the page list.
>> The page list can be different, several list might point to the same detail.
>> Until now I have been using page reference to return to the previous
>> page, and it works well.
>> However, passing the page reference to the constructor of the detail
>> page, means that page is not bookmarkable (unless I am mistaking
>> something)
>>
>> Is there a way a can pass the page reference as a request parameter,
>> and so make the page bookmarkable? (ex. by using id, page map, etc).
>> Of course if no page reference can be retraced from the map, then we
>> just ignore the back reference.
>>
>> Any ideas?
>>
>> - Nelson
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: PageReference as page parameter?
Posted by Igor Vaynberg <ig...@gmail.com>.
you can pass in the page id obtained from page#getpageid() as a
bookmarkable url, then to navigate back to the original page you can
do setResponsePage(new PageReference(pageid).getPage())
this will, however, leave you on a nonbookmarkable url when you come back.
if you want bookmarkable urls all the way around then you need to do
what stateless frameworks do, pass the return url to the detail page
as a parameter.
-igor
On Mon, Sep 17, 2012 at 3:07 PM, Nelson Segura <ns...@gmail.com> wrote:
> Hello,
> I have a very common pattern in which from a list, I can to detail of
> an element in the list.
> In the detail page I have a reference back to the page list.
> The page list can be different, several list might point to the same detail.
> Until now I have been using page reference to return to the previous
> page, and it works well.
> However, passing the page reference to the constructor of the detail
> page, means that page is not bookmarkable (unless I am mistaking
> something)
>
> Is there a way a can pass the page reference as a request parameter,
> and so make the page bookmarkable? (ex. by using id, page map, etc).
> Of course if no page reference can be retraced from the map, then we
> just ignore the back reference.
>
> Any ideas?
>
> - Nelson
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org