> >> > -igor
> >> >
> >>
> >> Thanks, it works like a charm. I did not know I could show an error
> >> message
> >> by calling "Component.error" and then use a filter to catch all error
> >> messages targeting a
gt;>
>> Thanks, it works like a charm. I did not know I could show an error
>> message
>> by calling "Component.error" and then use a filter to catch all error
>> messages targeting a specific FormComponent.
>>
>>
>>
d to have a wizard
and implement the "record_status" check process as you suggested to make
sure that the database is always consistent.
--
View this message in context:
http://www.nabble.com/User-name-validation---how-to-check-database-to-find-if-a-name-has--already-been-taken--tp256146
> > }
> >
> > -igor
> >
>
> Thanks, it works like a charm. I did not know I could show an error
> message
> by calling "Component.error" and then use a filter to catch all error
> messages targeting a specific FormComponent.
>
>
> --
> Vie
Thanks, it works like a charm. I did not know I could show an error message
by calling "Component.error" and then use a filter to catch all error
messages targeting a specific FormComponent.
--
View this message in context:
http://www.nabble.com/User-name-validation---how-
onal commands, e-mail: users-h...@wicket.apache.org
>>
>
> Can you be a little bit more specific? After I catch a nonuqniue
> exception,
> how should I change the page markup to present an error message? Any
> examples/references will be helpful.
>
>
>
--
View th
form {
onsubmit() {
try {
users.persist(getmodelobject());
} catch (usernamealreadyexistsexception e) {
error("error.username.exists");
}
}
}
-igor
On Fri, Sep 25, 2009 at 9:05 AM, Ryan Gravener wrote:
> I think you are overcomplicating things. Vali
http://www.nabble.com/User-name-validation---how-to-check-database-to-find-if-a-name-has--already-been-taken--tp25614625p25615006.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-u
I think you are overcomplicating things. Validate the users input, if
two users want the same name within 1 second of each request you
probably have bigger problems to deal with. Anyhow, when submit is
called, if you get a nonunique exception. Catch in dao/service and
throw an exception wicket
Hello,
I would like to get your suggestion about how to validate a user name input
by checking if the name has already been taken (exists in the back-end
database); and how to show feedback messages right next to the input field
if it has.
Typically, when a user registers to a website, he needs t
10 matches
Mail list logo
