> And it wont get any better until people like you improve it with their > findings... > The wiki is community based.
Sorry, I did not know that the changes were introduced as some kind of challenging game. I assumed that the Wicket developers had the changes done intentionally and updated the migration guide to simplify the task for their users. Tom On 07.02.2012 11:44, Martin Grigorov wrote: > On Tue, Feb 7, 2012 at 12:39 PM, Thomas Singer <[email protected]> wrote: >> Following Wicket 1.4 code: >> >> final RequestParameters parameters = new RequestParameters(); >> parameters.setParameters(new HashMap()); >> >> String path = ... >> parameters.setPath(path); >> final IRequestTarget requestTarget = RequestCycle.get().getProcessor() >> .getRequestCodingStrategy().targetForRequest(parameters); >> if (!(requestTarget instanceof IBookmarkablePageRequestTarget)) { >> return null; >> } >> >> return ((IBookmarkablePageRequestTarget)requestTarget).getPageClass(); >> >> does not compile in Wicket 1.5: RequestParameters is unknown, >> RequestCycle.get().getProcessor() is unknown, IBookmarkablePageRequestTarget >> is unknown, the migration guide is no help. > > And it wont get any better until people like you improve it with their > findings... > The wiki is community based. > >> >> Tom >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
