Hi, We were also plagued by these EOF errors since upgrade to Wicket 6 from 1.4. In the old Wicket the errors (which are not errors - it's an expected behavior when a user cancels navigation) were not reported in such aggressive manner, with long stack traces.
How is it possible to hide these errors or better convert them to a one-line WARN messages? Where is the best place to catch them? Regards, Andrew -- Andrew Schetinin On Sat, Jan 4, 2014 at 11:50 AM, Martin Grigorov <mgrigo...@apache.org>wrote: > Hi, > > > On Sat, Jan 4, 2014 at 1:06 AM, eaglei22 <jchojnack...@gmail.com> wrote: > >
