that would indeed explain it. 1.2 cathces that error and wants to display the error message but cant. thus the needed key.-IgorOn 2/1/06, David Leangen
<[EMAIL PROTECTED]> wrote:Interesting.
> i dont know why you didnt get that same error in 1.1, maybe you never> tried an invalid value? or maybe i
Interesting.
> i dont know why you didnt get that same error in 1.1, maybe you never
> tried an invalid value? or maybe in 1.1 you had
> ThrowExceptionOnMissingResource disabled in settings. if you have that
> disabled and no feedback panel you would have never seen an exception
> or the error.
but you are using validation implicity by specifinc QueryExpression.class parameter in the TextFieldlook at the constructor of TextField: public TextField(final String id, IModel model, Class type) {
super(id, model); add(new TypeValidator(type)); }it automatically adds a ty
> in 1.1 you must have had a formid.fieldid.TypeValidator key
> this same key should still work in 1.2
Sorry if I confused you.
I was trying to say that no, I did NOT have any such key in 1.1. I did
not use any type of validator, and no exception was thrown like it is
now in 1.2.
> in fact Type
in 1.1 you must have had a formid.fieldid.TypeValidator keythis same key should still work in 1.2in fact TypeValidator key would also work in 1.1, see
http://www.wicket-wiki.org.uk/wiki/index.php/Validation_Messagesafaik the transition should have been seamless as we did not change this part of wi
> it looks like you declared one of your form components with a type,
> like new TextField("id", model, Integer.class);
> this by default adds a typevalidator to your form component.
Yes, exactly!
> the key you need to build is TypeValidator=message
> or fieldid.TypeValidator=message
Ok, that
it looks like you declared one of your form components with a type, like new TextField("id", model, Integer.class);this by default adds a typevalidator to your form component.the key you need to build is TypeValidator=message
or fieldid.TypeValidator=message-IgorOn 2/1/06, David Leangen <[EMAIL PRO
If this mail is out of order, I apologise. Something weird is happening
with my mails, and they are not being received in order... They're also
taking a long time to reach the list.
> It
> looks like it searching for a property named "TypeValidator" in your
> properties files which it doesn't fin
I'm not aware it has changed (see
http://www.wicket-wiki.org.uk/wiki/index.php/Migrate-1.2 as well). It
looks like it searching for a property named "TypeValidator" in your
properties files which it doesn't find. Are you using any properties
files? What is the message the user gets in 1.1 on provid
I'm upgrading to version 1.2 and am having a few transition issues.
What do I need to do to get rid of this problem? I assume that
something's changed since 1.1...
Thanks!!
java.util.MissingResourceException: Unable to find resource:
TypeValidator
at
wicket.markup.html.form.validation.T
Hi;In the WebApplication class override method getHomePage(), somthing like this:public Class getHomePage() { return MyHomePage.class; }Regards, Ali
On 2/1/06, David Leangen <[EMAIL PROTECTED]> wrote:
I'm upgrading to version 1.2 and am having a few transition issues.What do I need to do
11 matches
Mail list logo