Hello
I used wicket to create small web application with search page. This page is
called many times in single minute, that is why we use stateless page for
smaller memory usage. On this page is stateless form with query text field
and after submit user is redirected to the same page with different page
parameters (setResponsePage(clazz,pageParameters);). We noticed that when
user clicked submit button wicket generate this page with old parameters,
then run osSubmit method and later generate this page with new parameters,
what call twice our search engine for the results! This is the normal
situation? Is any way to deal with this behaviour?
Best regards
KotFilemon
I used wicket to create small web application with search page. This page is
called many times in single minute, that is why we use stateless page for
smaller memory usage. On this page is stateless form with query text field
and after submit user is redirected to the same page with different page
parameters (setResponsePage(clazz,pageParameters);). We noticed that when
user clicked submit button wicket generate this page with old parameters,
then run osSubmit method and later generate this page with new parameters,
what call twice our search engine for the results! This is the normal
situation? Is any way to deal with this behaviour?
Best regards
KotFilemon