Re: Migrating WebRequestCycleProcessor from 1.4.x to 6.5.0
all these things can be accomplished from inside IRequestCycleListener -igor On Mon, May 6, 2013 at 10:26 PM, iamrakesh iamrakes...@rediffmail.com wrote: Hi, In resolve() method we're trying to catch handle InvalidUrlException to prevent exception due to multiple clicks on a button. In respond() method we're logging the request target [RequestCycle#getRequestTarget() value] and if it is of type AjaxRequestTarget we're trying to add components to request target which needs to updated on the page, this must be done just before the actual response is rendered. And in newRequestCodingStrategy() method, we're returning a custom implementation of org.apache.wicket.protocol.http.request.CryptedUrlWebRequestCodingStrategy class. This custom implementation overrides the encodeURL() method. Regards, Rakesh.A -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-WebRequestCycleProcessor-from-1-4-x-to-6-5-0-tp4658605p4658607.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Migrating WebRequestCycleProcessor from 1.4.x to 6.5.0
Hi, I am trying migration code from wicket v1.4 to v6.5.0, I've a custom implementation of WebRequestCycleProcessor, on migration wiki page I read that WebRequestcycleProcessor is removed, is there any replacement for this class? Regards, Rakesh.A -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-WebRequestCycleProcessor-from-1-4-x-to-6-5-0-tp4658605.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migrating WebRequestCycleProcessor from 1.4.x to 6.5.0
Hi, In resolve() method we're trying to catch handle InvalidUrlException to prevent exception due to multiple clicks on a button. In respond() method we're logging the request target [RequestCycle#getRequestTarget() value] and if it is of type AjaxRequestTarget we're trying to add components to request target which needs to updated on the page, this must be done just before the actual response is rendered. And in newRequestCodingStrategy() method, we're returning a custom implementation of org.apache.wicket.protocol.http.request.CryptedUrlWebRequestCodingStrategy class. This custom implementation overrides the encodeURL() method. Regards, Rakesh.A -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-WebRequestCycleProcessor-from-1-4-x-to-6-5-0-tp4658605p4658607.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org