That's perfect. Thanks so much.
Brian Mulholland
"For every complex problem, there is an answer that is clear, simple and
wrong."
--H.L. Mencken
"Politics is the art of looking for trouble, finding it everywhere,
diagnosing it incorrectly, and applying the wrong remedies."
--Groucho Marx
On
Hi,
FormComponent has a special error() method for ValidationErrors.
You're hitting another method on Component, that just accepts any
serializable:
((WebMarkupContainer) form.get("wmcCaptchaError")).error(new
ValidationError().addKey("CaptchaRequired"));
Try the following instead:
Yeah, it's definitely related to the component that the
ComponentFeedbackPanel relates to. If I use a TextField, it finds the
message perfectly. I change it to a web markup container or hiddenfield,
and it fails to find the message. Same name, same code doing the validation
and the adding of
The properties file is in the same package as the page, and has the same
prefix name, LandingPage_Cp10. Other errors added to TextFields and
whatnot from the SAME VALIDATOR are working that use messages from that
SAME FILE. I even can add the same message to a regular textfield in that
same
Hi,
We need to know the location of the i18n file, the package structure and
the component tree structure to be able to tell why Wicket cannot find it
...
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Aug 22, 2017 at 9:33 PM, Entropy
Works fine here: Messages show up with either button (and as you type too).
Sven
On 05/03/2013 11:11 PM, Taro Fukunaga wrote:
Hi,
I'm having a problem with validation in a form with ajax buttons. I am using
Wicket 6.7.0 and running Form Example: shows ajax form processing on my
local box (I
Would it be true that the entire form id from the page level down is needed?
tabs.panel. for instance? That seems to work.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Validation-messages-for-required-fields-using-form-id-tp3403212p3403612.html
Sent from the Users
On Thu, Mar 24, 2011 at 9:01 PM, mwilber matt.wil...@gmail.com wrote:
Would it be true that the entire form id from the page level down is
needed?
tabs.panel. for instance? That seems to work.
All of them should work.
More specific ones have bigger priority.
--
View this message in
first call setlabel on your formcomponent with the value that you want
to show up, then in the error message template use ${label} variable.
-igor
On Mon, Jun 7, 2010 at 10:54 AM, Brian Mulholland
blmulholl...@gmail.com wrote:
This is probably a stupid question, but when I set up a validation
Thank you, but it seems that only found resources are logged. Meanwhile I
have found out that I have to use a key like this:
myform.tabs.panel.myfield=My Field
where tabs is the id of my tabbed panel. But I haven't found a log message
that points to a missing key myform.tabs.panel.myfield.
Kai
try org.apache.wicket.Localizer
-igor
On Wed, Oct 22, 2008 at 1:55 AM, Kai Mütz [EMAIL PROTECTED] wrote:
Thank you, but it seems that only found resources are logged. Meanwhile I
have found out that I have to use a key like this:
myform.tabs.panel.myfield=My Field
where tabs is the id of
log4j.logger.org.apache.wicket.resource=DEBUG
should do it afair.
-igor
On Tue, Oct 21, 2008 at 8:16 AM, Kai Mütz [EMAIL PROTECTED] wrote:
Hi,
I have some problems with validation messages. Normally I set my validation
messages within the property files like this:
Required='${label}' is
12 matches
Mail list logo
