I think in my case WICKET-4197 was causing the problem. Ernesto
On Sat, Nov 5, 2011 at 5:34 PM, Ernesto Reinaldo Barreiro <[email protected]> wrote: > I´m also having issues with > org.apache.wicket.request.handler.ComponentNotFoundException and > current 1.5.x trunk... I did not stop to look carefully at them yet. > > Regards, > > Ernesto > > On Sat, Nov 5, 2011 at 5:28 PM, Bas Gooren <[email protected]> wrote: >> See https://issues.apache.org/jira/browse/WICKET-4163 for your first issue. >> You can ignore it (it's harmless) or use the workaround until 1.5.3 is >> released. >> >> Your second issue rings a bell (maybe other people reported this recently). >> It could also be related to >> https://issues.apache.org/jira/browse/WICKET-3618, although that is was >> fixed in a 1.5 release candidate... >> >> Op 5-11-2011 17:07, schreef hfriederichs: >>> >>> Hello, >>> >>> I am trying to migrate from 1.4.18 to 1.5.2. I followed the suggestions on >>> https://cwiki.apache.org/WICKET/migration-to-wicket-15.html >>> >>> I have a Wicket application with 6 tabs. After starting the server and a >>> browser-instance, I get: >>> [ WARN] 2011-11-05 17:00:26 >>> org.apache.wicket.request.handler.render.WebPageRenderer:162 - The >>> Buffered response should be handled by BufferedResponseRequestHandler. >>> >>> Just that. >>> >>> Then, on every action I try (click something, check a radiobutton), I >>> get: >>> >>> [ERROR] 2011-11-05 16:51:51 org.apache.wicket.DefaultExceptionMapper:114 >>> - Unexpected error occurred >>> java.lang.IllegalStateException: Header was already written to response! >>> at >>> >>> org.apache.wicket.protocol.http.HeaderBufferingWebResponse.checkHeader(HeaderBufferingWebResponse.java:64) >>> at >>> >>> org.apache.wicket.protocol.http.HeaderBufferingWebResponse.sendRedirect(HeaderBufferingWebResponse.java:112) >>> at >>> >>> org.apache.wicket.request.handler.render.WebPageRenderer.redirectTo(WebPageRenderer.java:136) >>> at >>> >>> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:266) >>> >>> And it keeps spawning these stacktraces... >>> Furthermore, as might be expected form an 'Unexpected Error', there's no >>> clue to the origin of this Exception in my application. Using development >>> mode doesn't add information. >>> >>> When I don't try to do something on the opening tab, and choose another >>> tab, >>> I get: >>> >>> org.apache.wicket.request.handler.ComponentNotFoundException: Could not >>> find >>> component etcetera >>> >>> Everything worked perfect with Wicket 1.4.18, and now nothing does. >>> >>> Please, where do I start? >>> >>> Many thanks in advance >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-wicket.1842946.n4.nabble.com/MIgration-to-1-5-2-seems-a-disaster-tp3993637p3993637.html >>> Sent from the Users forum mailing list archive at Nabble.com. >>> >>> --------------------------------------------------------------------- >>> 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]
