migrate to 1.5 setResponsePage-problem
In trying to migrate from wicket 1.4 to 1.5, all my setResponsePage calls get red in Eclipse. e.g: setResponsePage(WelcomePage.class, parameters); gets the error message: The method setResponsePage(ClassC, PageParameters) in the type Component is not applicable for the arguments (ClassWelcomePage, PageParameters) I can change the call to: setResponsePage(new WelcomePage(parameters)); , but this is quite some work for all the calls in the whole project. Why doesn`t the old method work? Cheers Terje Eithun, Norway -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/migrate-to-1-5-setResponsePage-problem-tp4659413.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: migrate to 1.5 setResponsePage-problem
Hi, The method is still there: https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/Component.java?source=cc#L3168 Try to build with javac/Maven or any other tool but Eclipse. On Wed, Jun 12, 2013 at 2:22 PM, terjeeit terje.eit...@gmail.com wrote: In trying to migrate from wicket 1.4 to 1.5, all my setResponsePage calls get red in Eclipse. e.g: setResponsePage(WelcomePage.class, parameters); gets the error message: The method setResponsePage(ClassC, PageParameters) in the type Component is not applicable for the arguments (ClassWelcomePage, PageParameters) I can change the call to: setResponsePage(new WelcomePage(parameters)); , but this is quite some work for all the calls in the whole project. Why doesn`t the old method work? Cheers Terje Eithun, Norway -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/migrate-to-1-5-setResponsePage-problem-tp4659413.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: migrate to 1.5 setResponsePage-problem
Thanks, yeah I figured it was still there. It was the packet-structure that didin`t update correctly. What before was:org.apache.wicket.PageParameters is now: org.apache.wicket.request.mapper.parameter.PageParameters appearently. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/migrate-to-1-5-setResponsePage-problem-tp4659413p4659418.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
