[1.4.6] inconsistent setResponsePage behavior in AjaxButton , with 1.4.5

2010-02-09 Thread smallufo 
Suppose inside a BookmarkablePage which is mounted to CurrentPage ,
there is an AjaxButton , when clicked , it will
setResponsePage(CurrentPage.class , pps)

If a user is browsing http://foo.bar/app/CurrentPage/key/value , and submit
the AjaxButton ,
In 1.4.5 , he will be redirect to http://foo.bar/app/CurrentPage/key/value
, it is correct
But in 1.4.6 , he will be redirect to
http://foo.bar/app/CurrentPage/key/CurrentPage/key/value
, it is WRONG

I think it is related to wicket2312 patch.

Re: [1.4.6] inconsistent setResponsePage behavior in AjaxButton , with 1.4.5

2010-02-09 Thread smallufo 
I've submitted it to JIRA
https://issues.apache.org/jira/browse/WICKET-2735
https://issues.apache.org/jira/browse/WICKET-2735

2010/2/10 smallufo small...@gmail.com

 Suppose inside a BookmarkablePage which is mounted to CurrentPage ,
 there is an AjaxButton , when clicked , it will
 setResponsePage(CurrentPage.class , pps)

 If a user is browsing http://foo.bar/app/CurrentPage/key/value , and
 submit the AjaxButton ,
 In 1.4.5 , he will be redirect to http://foo.bar/app/CurrentPage/key/value
 , it is correct
 But in 1.4.6 , he will be redirect to 
 http://foo.bar/app/CurrentPage/key/CurrentPage/key/value
 , it is WRONG

 I think it is related to wicket2312 patch.

Re: [1.4.6] inconsistent setResponsePage behavior in AjaxButton , with 1.4.5

2010-02-09 Thread vineet semwal 
i think it's issue 2717 in 1.4.6 which has been fixed,you can confirm the
correct behaviour
in 1.4.x.

On Wed, Feb 10, 2010 at 10:19 AM, smallufo small...@gmail.com wrote:

 Suppose inside a BookmarkablePage which is mounted to CurrentPage ,
 there is an AjaxButton , when clicked , it will
 setResponsePage(CurrentPage.class , pps)

 If a user is browsing http://foo.bar/app/CurrentPage/key/value , and
 submit
 the AjaxButton ,
 In 1.4.5 , he will be redirect to http://foo.bar/app/CurrentPage/key/value
 , it is correct
 But in 1.4.6 , he will be redirect to
 http://foo.bar/app/CurrentPage/key/CurrentPage/key/value
 , it is WRONG

 I think it is related to wicket2312 patch.




-- 
regards,
Vineet Semwal