You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Anthony DePalma <fa...@gmail.com> on 2010/02/06 00:19:36 UTC
Bug with setResponsePage and PageParameters for wicket 1.4.6?
I noticed something strange, I have a search panel on all pages that
contains a single form like so:
final Form<SearchParams> searchForm = new
StatelessForm<SearchParams>("searchForm", model) {
@Override
protected void onSubmit() {
String query = getModelObject().getQuery();
setResponsePage(SearchResultsPage.class, new PageParameters(
SearchResultsPage.PARAM_QUERY + "=" + query));
setRedirect(true);
}
};
My SearchResultsPage is mapped to /search, so after a query i get
redirected to /search/query/some+query. After the first submit
everything works (the submit is happening from a different page), I
get the redirect and see the results. But then if I try to use the
form from that page, I get redirected with the previous search params
in the url, like so: /search/query/search/query/second+query. Im not
sure how this is happening since I am passing a class and new page
parameters. The String query inside the onSubmit has the correct
value, its not appending any of the previous parameters, and besides,
this only happens with 1.4.6. I tried it on 1.4.4 and 1.4.5 and it
worked fine with the same code. Any ideas?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment
mode
Posted by Igor Vaynberg <ig...@gmail.com>.
QuickStart strikes again :)
-igor
On Friday, February 12, 2010, Andreas Lüdtke <sa...@t-online.de> wrote:
> Igor,
>
> I made a quickstart and found that it's not a wicket issue but a tomcat
> issue. I installed tomcat 6.0.24 and configured it in Netbeans and now it
> works as expected.
>
> Thanks
>
> Andreas
>
>> -----Original Message-----
>> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
>> Sent: Tuesday, February 09, 2010 5:19 PM
>> To: users@wicket.apache.org; sam.luedtke@t-online.de
>> Subject: Re: AbstractAjaxTimerBehavior#onTimer() doesn't work
>> in deployment mode
>>
>> feel free to open a jira issue attaching a quickstart that reproduces
>> the problem.
>>
>> -igor
>>
>> On Tue, Feb 9, 2010 at 12:37 AM, Andreas Lüdtke
>> <sa...@t-online.de> wrote:
>> > Can someone please confirm if this is a bug? If yes, I will
>> create a JIRA
>> > issue if I'm allowed to do that.
>> >
>> > Thanks
>> >
>> > Andreas
>> >
>> >> -----Original Message-----
>> >> From: Andreas Lüdtke [mailto:sam.luedtke@t-online.de]
>> >> Sent: Saturday, February 06, 2010 7:43 PM
>> >> To: users@wicket.apache.org
>> >> Subject: AbstractAjaxTimerBehavior#onTimer() doesn't work in
>> >> deployment mode
>> >>
>> >> Hi,
>> >>
>> >> I'm using wicket 1.4.6 and saw that the onTimer method of an
>> >> AbstractAjaxTimerBehavior object isn't called, when I switch
>> >> vom development
>> >> mode to deployment mode. This happens also with wicket 1.4.5.
>> >>
>> >> Is there something I need to do to get it working in
>> deployment mode?
>> >>
>> >> In addition, after calling AbstractAjaxTimerBehavior.stop()
>> >> the onTimer
>> >> method is still called (of course only in development mode). ;-)
>> >>
>> >> If someone finds the time to fix this, I would be glad if
>> >> this person could
>> >> implement a restart() method to start the timer after it has
>> >> been stopped.
>> >>
>> >> Andreas
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > 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: AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment mode
Posted by Andreas Lüdtke <sa...@t-online.de>.
Igor,
I made a quickstart and found that it's not a wicket issue but a tomcat
issue. I installed tomcat 6.0.24 and configured it in Netbeans and now it
works as expected.
Thanks
Andreas
> -----Original Message-----
> From: Igor Vaynberg [mailto:igor.vaynberg@gmail.com]
> Sent: Tuesday, February 09, 2010 5:19 PM
> To: users@wicket.apache.org; sam.luedtke@t-online.de
> Subject: Re: AbstractAjaxTimerBehavior#onTimer() doesn't work
> in deployment mode
>
> feel free to open a jira issue attaching a quickstart that reproduces
> the problem.
>
> -igor
>
> On Tue, Feb 9, 2010 at 12:37 AM, Andreas Lüdtke
> <sa...@t-online.de> wrote:
> > Can someone please confirm if this is a bug? If yes, I will
> create a JIRA
> > issue if I'm allowed to do that.
> >
> > Thanks
> >
> > Andreas
> >
> >> -----Original Message-----
> >> From: Andreas Lüdtke [mailto:sam.luedtke@t-online.de]
> >> Sent: Saturday, February 06, 2010 7:43 PM
> >> To: users@wicket.apache.org
> >> Subject: AbstractAjaxTimerBehavior#onTimer() doesn't work in
> >> deployment mode
> >>
> >> Hi,
> >>
> >> I'm using wicket 1.4.6 and saw that the onTimer method of an
> >> AbstractAjaxTimerBehavior object isn't called, when I switch
> >> vom development
> >> mode to deployment mode. This happens also with wicket 1.4.5.
> >>
> >> Is there something I need to do to get it working in
> deployment mode?
> >>
> >> In addition, after calling AbstractAjaxTimerBehavior.stop()
> >> the onTimer
> >> method is still called (of course only in development mode). ;-)
> >>
> >> If someone finds the time to fix this, I would be glad if
> >> this person could
> >> implement a restart() method to start the timer after it has
> >> been stopped.
> >>
> >> Andreas
> >
> >
> >
> ---------------------------------------------------------------------
> > 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: AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment
mode
Posted by Igor Vaynberg <ig...@gmail.com>.
feel free to open a jira issue attaching a quickstart that reproduces
the problem.
-igor
On Tue, Feb 9, 2010 at 12:37 AM, Andreas Lüdtke <sa...@t-online.de> wrote:
> Can someone please confirm if this is a bug? If yes, I will create a JIRA
> issue if I'm allowed to do that.
>
> Thanks
>
> Andreas
>
>> -----Original Message-----
>> From: Andreas Lüdtke [mailto:sam.luedtke@t-online.de]
>> Sent: Saturday, February 06, 2010 7:43 PM
>> To: users@wicket.apache.org
>> Subject: AbstractAjaxTimerBehavior#onTimer() doesn't work in
>> deployment mode
>>
>> Hi,
>>
>> I'm using wicket 1.4.6 and saw that the onTimer method of an
>> AbstractAjaxTimerBehavior object isn't called, when I switch
>> vom development
>> mode to deployment mode. This happens also with wicket 1.4.5.
>>
>> Is there something I need to do to get it working in deployment mode?
>>
>> In addition, after calling AbstractAjaxTimerBehavior.stop()
>> the onTimer
>> method is still called (of course only in development mode). ;-)
>>
>> If someone finds the time to fix this, I would be glad if
>> this person could
>> implement a restart() method to start the timer after it has
>> been stopped.
>>
>> Andreas
>
>
> ---------------------------------------------------------------------
> 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: AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment mode
Posted by Andreas Lüdtke <sa...@t-online.de>.
Can someone please confirm if this is a bug? If yes, I will create a JIRA
issue if I'm allowed to do that.
Thanks
Andreas
> -----Original Message-----
> From: Andreas Lüdtke [mailto:sam.luedtke@t-online.de]
> Sent: Saturday, February 06, 2010 7:43 PM
> To: users@wicket.apache.org
> Subject: AbstractAjaxTimerBehavior#onTimer() doesn't work in
> deployment mode
>
> Hi,
>
> I'm using wicket 1.4.6 and saw that the onTimer method of an
> AbstractAjaxTimerBehavior object isn't called, when I switch
> vom development
> mode to deployment mode. This happens also with wicket 1.4.5.
>
> Is there something I need to do to get it working in deployment mode?
>
> In addition, after calling AbstractAjaxTimerBehavior.stop()
> the onTimer
> method is still called (of course only in development mode). ;-)
>
> If someone finds the time to fix this, I would be glad if
> this person could
> implement a restart() method to start the timer after it has
> been stopped.
>
> Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
AbstractAjaxTimerBehavior#onTimer() doesn't work in deployment mode
Posted by Andreas Lüdtke <sa...@t-online.de>.
Hi,
I'm using wicket 1.4.6 and saw that the onTimer method of an
AbstractAjaxTimerBehavior object isn't called, when I switch vom development
mode to deployment mode. This happens also with wicket 1.4.5.
Is there something I need to do to get it working in deployment mode?
In addition, after calling AbstractAjaxTimerBehavior.stop() the onTimer
method is still called (of course only in development mode). ;-)
If someone finds the time to fix this, I would be glad if this person could
implement a restart() method to start the timer after it has been stopped.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Bug with setResponsePage and PageParameters for wicket 1.4.6?
Posted by Alex Objelean <al...@yahoo.com>.
I think it is a know bug (http://issues.apache.org/jira/browse/WICKET-2717)
and was is already fixed in trunk. Hopefully there will be a 1.4.7 release
very soon.
Alex Objelean
fatefree wrote:
>
> I noticed something strange, I have a search panel on all pages that
> contains a single form like so:
>
> final Form<SearchParams> searchForm = new
> StatelessForm<SearchParams>("searchForm", model) {
> @Override
> protected void onSubmit() {
> String query = getModelObject().getQuery();
> setResponsePage(SearchResultsPage.class, new PageParameters(
> SearchResultsPage.PARAM_QUERY + "=" + query));
> setRedirect(true);
> }
> };
>
> My SearchResultsPage is mapped to /search, so after a query i get
> redirected to /search/query/some+query. After the first submit
> everything works (the submit is happening from a different page), I
> get the redirect and see the results. But then if I try to use the
> form from that page, I get redirected with the previous search params
> in the url, like so: /search/query/search/query/second+query. Im not
> sure how this is happening since I am passing a class and new page
> parameters. The String query inside the onSubmit has the correct
> value, its not appending any of the previous parameters, and besides,
> this only happens with 1.4.6. I tried it on 1.4.4 and 1.4.5 and it
> worked fine with the same code. Any ideas?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://old.nabble.com/Bug-with-setResponsePage-and-PageParameters-for-wicket-1.4.6--tp27475350p27481276.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org