if we're getting rid of PageLink entirely, you mean:
new Link("previousPage")
{
public void onClick() { setResponsePage(prevPage); }
public boolean linksTo(Page page) { return page.equals(prevPage); }
}
Johan Compagner wrote:
>
> instead of doing this:
>
> PageLink link = new PageLink("previouspage", prevPage);
>
> you have to do:
>
> final Page prevPage = xx;
> PageLink link = new PageLink("previouspage", new IPageLink()
> {
> private static final long serialVersionUID = 1L;
>
> public Page getPage()
> {
> // Create page using page factory
> return prevPage;
> }
>
> public Class getPageIdentity()
> {
> return prevPage.getClass();
> }
> });
>
> johan
>
>
> On 2/27/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
>>
>> * Martijn Dashorst:
>>
>> > I see it as a pretty major api break. Considering that everyone
>> > on our project uses the construct to return quickly to the
>> > previous page, which is a very valid usecase.
>>
>> To be sure that there is no misunderstanding, can you provide the
>> exact source code that illustrates your opinion please?
>> --
>> Jean-Baptiste Quenot
>> aka John Banana Qwerty
>> http://caraldi.com/jbq/
>>
>
>
--
View this message in context:
http://www.nabble.com/VOTE%3A-remove-PageLink%28String%2CPage%29-constructor-tf3274259.html#a9186573
Sent from the Wicket - Dev mailing list archive at Nabble.com.
