Re: Button not visible, except that it is...
Nevermind, it's because he didn't have that higher panel in the target for that event. So he set the visibility to false without realizing it, and didn't add it to the target. Mystery Solved. Thanks as always for the quick response. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567p4678576.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
Validation messages from properties file not working.
We have a javascript widget on our page that doesn't have a wicket form
component bound to it. We just get the value from the request. We have a
ComponentFeedbackPanel (CFP) because that's what we do with all of our
messages. We fed a WebMarkupContainer (WMC) that is around the CFP in as
the Component for the CFP to relate to. We add the validation message to
that WMC, and the error DOES show.
However, for some reason it's not finding the validation key from the
property file. Every other error done the same way DOES, so i have to guess
that it's because we are binding to the WMC that it's not working?
Properties File line:
CaptchaRequired=The CAPTCHA verification is required. Please complete it to
continue.
Where we add the key (in an abstractformvalidator):
((WebMarkupContainer) form.get("wmcCaptchaError")).error(new
ValidationError().addKey("CaptchaRequired"));
Ideas?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Validation-messages-from-properties-file-not-working-tp4678575.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
Re: Button not visible, except that it is...
The isVisibleInHierarchy() method returns false. Stepped into that and realized that my co-worker was setting a parent panel false in a panel further up the hierarchy in the onConfigure of a behavior, which fires once at page load and again after the button click that makes this other button/panel visible. But that code hard-coded it to false. It should have rendered the whole panel invisible I would think. Which is not what we want, but I am confused why the panel rendered as visible. onConfigure() javadoc says it fires before render. So that is confusing to me. But we definitely have the problem figured out. Any idea why the panel rendered as if visible? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Button-not-visible-except-that-it-is-tp4678567p4678574.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
Re: why is DefaultNestedTree component treated as property within PropertyResolver ?
Hi Sven, I solved the problem related to PropertyResolver by this way: the model of my "Modal"-extension is now a "Model" (String) and not "CompoundPropertyModel". My next problem is: the tree isn't expandable. I'll try to fix it before I post another question. Thank you -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/why-is-DefaultNestedTree-component-treated-as-property-within-PropertyResolver-tp4678549p4678572.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
