Wicket hidden field in form: exception when injecting values?

Since Wicket is open source, you can of course understand some of this by looking at the source.

Since Wicket is open source, you can of course understand some of this by looking at the source. I believe that field is used for Ajax event handling, and is given a value by a JavaScript attached to the link as an onclick method at rendering. You can see where this javascript is made by looking at the source code in org.apache.wicket.markup.html.form.

SubmitLink method getTriggerJavaScript and you can see the resulting markup using firebug. Many of the methods in Wicket are final so you can't override them, and marked with Javadoc exhortations not to call them yourself, and particularly in the area of form submission where this field is used, this call happens earlier in the cycle than most of the standard hooks for subclass form handling, so trying to catch the WicketRuntimeException and handle it in a way specific to this field might be difficult. Catching it and showing a custom error page can of course be done as described at the wiki page on error pages, and this is a good thing to do anyway.

Thx. I was hoping to get around that exception (do some sanity check or so) but a error page is also a solution – nebenmir Sep 9 '10 at 10:54.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.