Hey guys,

I have some business logic where when the set method is called, it first
validates the value.  In finding a “bad” value, it then throws a custom
validation exception.  We use this pattern all over the place.

Is there some way to handle this situation so that it’s a valid wicket
validation error?

Thanks for any tips.

-Lon (Wicket Newb :D)

Reply via email to