right now you have a few choices:
you can load that .properties file yourself from inside your validator
you can put these properties into application-scoped .properties file.
you can also add an rfe into our jira to allow validators to have their own
.properties bundles.
-igor
On 8/18/07,
Hi Igor
The error message says:
Could not locate error message for error:
[org.apache.wicket.validation.ValidationError message=[null],
keys=[notFound, ClassValidator], variables=[]]
notFound - is my key
ClassValidator - is the name of the class
the .propeties file is together with .class file
On 8/18/07, Stojce Dimski [EMAIL PROTECTED] wrote:
Hi Igor
The error message says:
Could not locate error message for error:
[org.apache.wicket.validation.ValidationError message=[null],
keys=[notFound, ClassValidator], variables=[]]
the problem looks like is that its looking for a
Hi Igor,
First thing, thanks, your hints gave me the direction and I solved the
issue... I like the approach 'Classname.Key' and I think it's right for
this category of generic validators as are those in 'validator'
package.
It was just a question of overriding one method:
@Override
public void
im not sure exactly what your usecase is.
we have something that is kind of similar, namely new TextField(number,
Integer.class); which would type convert the entered string into an Integer
and error out if the conversion could not be performed.
but i dont think this is the exact match to
