Hey Sven, I considered this, but realized that models don’t have access to the component, so I wasn’t sure how I would report the errors. Any tips would be appreciated.
-Lon On Thu, May 19, 2016 at 7:08 AM, Sven Meier <s...@meiers.net> wrote: > Hi, > > you could use a custom model wrapper catching your exceptions and > reporting them as error messages. > > Have fun > Sven > > > > On 19.05.2016 00:23, Lon Varscsak wrote: > >> 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) >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
