Please continue this topic in a separate thread. Thanks! :-) On Wed, Sep 28, 2011 at 9:51 AM, Emond Papegaaij <[email protected]> wrote: > It is your mapper that triggers this issue, therefore it is easy to work > around. You only have to prevent the code added for WIKCET-4014 from being > called, like this: > > public Url mapHandler(IRequestHandler requestHandler) { > if (requestHandler instanceof ListenerInterfaceRequestHandler) > return null; > return super.mapHandler(requestHandler); > } > > I've tested it on your quickstart, and it works. > > Emond > > On Tuesday 27 September 2011 21:25:41 [email protected] wrote: >> (non-binding) -1 >> >> Thanks for reviewing WICKET-4087. >> >> Sorry, I don't have a workaround. This might be a misunderstanding. It >> is the mapper that triggers this issue. Sure it is a corner case. But >> a very simple one, and the changes might cause other hard to find >> issues. Most Bugs are corner cases. >> >> Bernard >> >> On Tue, 27 Sep 2011 15:26:12 +0200, you wrote: >> >(non-binding) +1 >> >Our application is running fine on 1.5.1. De reported issues are fixed, as >> >far as we could reproduce them. >> > >> >Wrt WICKET-4087, I think this is a corner case and should be easy to work >> >around, because Bernard already has his own mapper. The change was >> >introduced with the fix for WICKET-4014. >
-- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
