Hi,
don't know whether this is a bug so I'll ask here first. In the wicket tree
examples, when I get a WicketRuntimeException in the
org.apache.wicket.examples.tree.BeginnersTreePage when I set a model to the
page as follows:
public BeginnersTreePage()
{
setDefaultModel(new
Yes, that is all understood. However, since Servlet 3.0 you can switch-off
url rewriting for session ids using the tracking mode setting. And redirect
to buffer is the default wicket strategy. It might not be clear to most
wicket users that these two features together can lead to the endless
Hi,
when I select COOKIE in the web.xml and
disable cookies in the browser, I run into endless redirects for buffered
responses. You can see this behavior, e.g., in the forminput example of the
wicket-examples project.
Not sure, whether this is a bug. After all, how should wicket know that the
I have implemented a root form R and a nested form N which has R as a parent
form. I would like to stop N from being processed when R has been submitted.
I've tried to do so by implementing IFormVisitorParticipant.processChildren.
However, I have not been able to distinguish which of the two
vov wrote:
But question is still open:)
Look to example
public static boolean visibleFlag = true;
public VisibilityButtonTest()
{
FormVoid form = new FormVoid(form);
add(form);
AjaxButton ajaxButton = new AjaxButton(button1)
{
@Override
public
I have an AjaxButton with
@Override
public boolean isVisible() {
return someFlag;
}
In a race condition, if user B sets someFlag to false, and then user A
clicks the button A gets the following exception
org.apache.wicket.WicketRuntimeException: Submit Button buttonName ... is
not visible
Thanks. That would have solved it. I am using setVisible(someFlag) now. Doh!
;)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/org-apache-wicket-WicketRuntimeException-Submit-Button-is-not-visible-tp2282413p2282534.html
Sent from the Wicket - User mailing list
Hi,
I use @AuthorizeInstantiation annotations to protect ajax components from
unauthorized instantiation. I use mounted bookmarkable pages. I just ran
into the following problem when the sign-in page redirects after successful
authentication:
When the url path contains more than 3 slashes the
