Thanks for the fast response.
I've tried to test it with a simple test page, containing one AjaxLink:
public class TestPage extends WebPage {
public TestPage() {
}
@Override
protected void onInitialize() {
super.onInitialize();
add(new AjaxLink<Void>("link") {
private static final long serialVersionUID =
1135836169949178116L;
@Override
public void onClick(AjaxRequestTarget target) {
target.appendJavascript("alert('test')");
}
});
}
}
In this scenario the ajax link is working fine, but in chrome 9 the id's are
always incremented with 2, while in firefox 3.6 it's a bit strange - on the
first reload the id is incremented with 3, on the second time with 4 and
after this on every reload the id is incremented by 1 (this is a repeated
pattern that happens every time).
I've also tried with the same page, but this time containing only a Form
(stateful):
public class TestPage extends WebPage {
public TestPage() {
}
@Override
protected void onInitialize() {
super.onInitialize();
add(new Form<Void>("form"));
}
}
The result with both pages is the same, the second page doesn't have any
links. Can those page-not-found requests that lead to the incrementing ids
lead to a slower page load time and increased load on the server? Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Custom-error-404-page-and-page-id-s-tp3220118p3220233.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
