Re: 1.4 trunk broken?
Yeah, we could, but then I'd have to make up a new version number for it, since the release plugin doesn't allow SNAPSHOT dependencies. If you guys are going to have rc7 out the door soon, I can just wait. The rc4 release works just fine. On Wed, Jul 8, 2009 at 11:38 AM, Igor Vaynberg wrote: > you can always build your own jar from trunk > > -igor > > On Wed, Jul 8, 2009 at 4:43 AM, James > Carman wrote: >> Yeah, there was a message that just sent out about it. It's >> WICKET-2346. When can we expect a new release? This is a nasty bug >> in our production environment (yes, I know I shouldn't be using an rc >> in production, but we didn't want to have to change the code to >> genericize it after an "official" 1.4 release). For now, we're going >> to back out to 1.4-rc4. >> >> >> On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner wrote: >>> i think in trunk it should be fixed. >>> >>> On Wed, Jul 8, 2009 at 13:20, James Carman >>> wrote: >>> >>>> Have we fixed this? I'm getting the same error. >>>> >>>> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner >>>> wrote: >>>> > The problem occurs when I klicked around on a page an then deploy a new >>>> version of the app. >>>> > When I klick on a page link now then the error occurs. In former trunk >>>> versions and all former wicket version I was redirected to the >>>> application's >>>> homepage. >>>> > >>>> > Stefan >>>> > >>>> > -Ursprüngliche Nachricht- >>>> > Von: Johan Compagner [mailto:jcompag...@gmail.com] >>>> > Gesendet: Dienstag, 16. Juni 2009 20:19 >>>> > An: users@wicket.apache.org >>>> > Betreff: Re: 1.4 trunk broken? >>>> > >>>> > i do remember one change for that invalidurlexception >>>> > (that we should throw that as an exception instead of just a page expired >>>> or >>>> > something) >>>> > >>>> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner >>>> wrote: >>>> > >>>> >> Using current 1.4 trunk gives me the error >>>> >> >>>> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: >>>> >> Cannot find the rendered page in session [pagemap=nu >>>> >> ll,componentPath=1,versionNumber=0] >>>> >> org.apache.wicket.protocol.http.request.InvalidUrlException: >>>> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the >>>> >> rendered >>>> >> page in session [pagemap=null,componentPath=1,versionNumber=0] >>>> >> at >>>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ >>>> >> estCycleProcessor.java:250) >>>> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >>>> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >>>> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >>>> >> at >>>> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 >>>> >> ) >>>> >> at >>>> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: >>>> >> 289) >>>> >> at >>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >>>> >> tionFilterChain.java:235) >>>> >> at >>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >>>> >> erChain.java:206) >>>> >> at >>>> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte >>>> >> r.java:96) >>>> >> at >>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >>>> >> tionFilterChain.java:235) >>>> >> at >>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >>>> >> erChain.java:206) >>>> >> at >>>> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv >>>> >> e.java:235) >>>> >> at >>>> &g
Re: 1.4 trunk broken?
you can always build your own jar from trunk -igor On Wed, Jul 8, 2009 at 4:43 AM, James Carman wrote: > Yeah, there was a message that just sent out about it. It's > WICKET-2346. When can we expect a new release? This is a nasty bug > in our production environment (yes, I know I shouldn't be using an rc > in production, but we didn't want to have to change the code to > genericize it after an "official" 1.4 release). For now, we're going > to back out to 1.4-rc4. > > > On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner wrote: >> i think in trunk it should be fixed. >> >> On Wed, Jul 8, 2009 at 13:20, James Carman >> wrote: >> >>> Have we fixed this? I'm getting the same error. >>> >>> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner >>> wrote: >>> > The problem occurs when I klicked around on a page an then deploy a new >>> version of the app. >>> > When I klick on a page link now then the error occurs. In former trunk >>> versions and all former wicket version I was redirected to the application's >>> homepage. >>> > >>> > Stefan >>> > >>> > -Ursprüngliche Nachricht- >>> > Von: Johan Compagner [mailto:jcompag...@gmail.com] >>> > Gesendet: Dienstag, 16. Juni 2009 20:19 >>> > An: users@wicket.apache.org >>> > Betreff: Re: 1.4 trunk broken? >>> > >>> > i do remember one change for that invalidurlexception >>> > (that we should throw that as an exception instead of just a page expired >>> or >>> > something) >>> > >>> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner >>> wrote: >>> > >>> >> Using current 1.4 trunk gives me the error >>> >> >>> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: >>> >> Cannot find the rendered page in session [pagemap=nu >>> >> ll,componentPath=1,versionNumber=0] >>> >> org.apache.wicket.protocol.http.request.InvalidUrlException: >>> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the >>> >> rendered >>> >> page in session [pagemap=null,componentPath=1,versionNumber=0] >>> >> at >>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ >>> >> estCycleProcessor.java:250) >>> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >>> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >>> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >>> >> at >>> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 >>> >> ) >>> >> at >>> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: >>> >> 289) >>> >> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >>> >> tionFilterChain.java:235) >>> >> at >>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >>> >> erChain.java:206) >>> >> at >>> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte >>> >> r.java:96) >>> >> at >>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >>> >> tionFilterChain.java:235) >>> >> at >>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >>> >> erChain.java:206) >>> >> at >>> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv >>> >> e.java:235) >>> >> at >>> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv >>> >> e.java:191) >>> >> at >>> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs >>> >> sociationValve.java:190) >>> >> at >>> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j >>> >> ava:92) >>> >> at >>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( >>> >> SecurityContextEstablishmentValve.java:126) >>> >> at >>>
Re: 1.4 trunk broken?
Yeah, there was a message that just sent out about it. It's WICKET-2346. When can we expect a new release? This is a nasty bug in our production environment (yes, I know I shouldn't be using an rc in production, but we didn't want to have to change the code to genericize it after an "official" 1.4 release). For now, we're going to back out to 1.4-rc4. On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner wrote: > i think in trunk it should be fixed. > > On Wed, Jul 8, 2009 at 13:20, James Carman > wrote: > >> Have we fixed this? I'm getting the same error. >> >> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner >> wrote: >> > The problem occurs when I klicked around on a page an then deploy a new >> version of the app. >> > When I klick on a page link now then the error occurs. In former trunk >> versions and all former wicket version I was redirected to the application's >> homepage. >> > >> > Stefan >> > >> > -Ursprüngliche Nachricht----- >> > Von: Johan Compagner [mailto:jcompag...@gmail.com] >> > Gesendet: Dienstag, 16. Juni 2009 20:19 >> > An: users@wicket.apache.org >> > Betreff: Re: 1.4 trunk broken? >> > >> > i do remember one change for that invalidurlexception >> > (that we should throw that as an exception instead of just a page expired >> or >> > something) >> > >> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner >> wrote: >> > >> >> Using current 1.4 trunk gives me the error >> >> >> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: >> >> Cannot find the rendered page in session [pagemap=nu >> >> ll,componentPath=1,versionNumber=0] >> >> org.apache.wicket.protocol.http.request.InvalidUrlException: >> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the >> >> rendered >> >> page in session [pagemap=null,componentPath=1,versionNumber=0] >> >> at >> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ >> >> estCycleProcessor.java:250) >> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >> >> at >> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 >> >> ) >> >> at >> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: >> >> 289) >> >> at >> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >> >> tionFilterChain.java:235) >> >> at >> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >> >> erChain.java:206) >> >> at >> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte >> >> r.java:96) >> >> at >> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >> >> tionFilterChain.java:235) >> >> at >> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >> >> erChain.java:206) >> >> at >> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv >> >> e.java:235) >> >> at >> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv >> >> e.java:191) >> >> at >> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs >> >> sociationValve.java:190) >> >> at >> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j >> >> ava:92) >> >> at >> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( >> >> SecurityContextEstablishmentValve.java:126) >> >> at >> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S >> >> ecurityContextEstablishmentValve.java:70) >> >> at >> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java >> >> :127) >> >> at >> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java >> >> :102) >> >> at >> >> org.jboss
Re: 1.4 trunk broken?
i think in trunk it should be fixed. On Wed, Jul 8, 2009 at 13:20, James Carman wrote: > Have we fixed this? I'm getting the same error. > > On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner > wrote: > > The problem occurs when I klicked around on a page an then deploy a new > version of the app. > > When I klick on a page link now then the error occurs. In former trunk > versions and all former wicket version I was redirected to the application's > homepage. > > > > Stefan > > > > -Ursprüngliche Nachricht- > > Von: Johan Compagner [mailto:jcompag...@gmail.com] > > Gesendet: Dienstag, 16. Juni 2009 20:19 > > An: users@wicket.apache.org > > Betreff: Re: 1.4 trunk broken? > > > > i do remember one change for that invalidurlexception > > (that we should throw that as an exception instead of just a page expired > or > > something) > > > > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner > wrote: > > > >> Using current 1.4 trunk gives me the error > >> > >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: > >> Cannot find the rendered page in session [pagemap=nu > >> ll,componentPath=1,versionNumber=0] > >> org.apache.wicket.protocol.http.request.InvalidUrlException: > >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the > >> rendered > >> page in session [pagemap=null,componentPath=1,versionNumber=0] > >>at > >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ > >> estCycleProcessor.java:250) > >>at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) > >>at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) > >>at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) > >>at > >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 > >> ) > >>at > >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: > >> 289) > >>at > >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > >> tionFilterChain.java:235) > >>at > >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > >> erChain.java:206) > >>at > >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte > >> r.java:96) > >>at > >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > >> tionFilterChain.java:235) > >>at > >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > >> erChain.java:206) > >>at > >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv > >> e.java:235) > >>at > >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv > >> e.java:191) > >>at > >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs > >> sociationValve.java:190) > >>at > >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j > >> ava:92) > >>at > >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( > >> SecurityContextEstablishmentValve.java:126) > >>at > >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S > >> ecurityContextEstablishmentValve.java:70) > >>at > >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java > >> :127) > >>at > >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java > >> :102) > >>at > >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn > >> ectionValve.java:158) > >>at > >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. > >> java:109) > >>at > >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3 > >> 30) > >>at > >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82 > >> 9) > >>at > >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( > >> Http11Protocol.java:598) > >>at > >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) > >>at java.la
Re: 1.4 trunk broken?
Have we fixed this? I'm getting the same error. On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner wrote: > The problem occurs when I klicked around on a page an then deploy a new > version of the app. > When I klick on a page link now then the error occurs. In former trunk > versions and all former wicket version I was redirected to the application's > homepage. > > Stefan > > -Ursprüngliche Nachricht- > Von: Johan Compagner [mailto:jcompag...@gmail.com] > Gesendet: Dienstag, 16. Juni 2009 20:19 > An: users@wicket.apache.org > Betreff: Re: 1.4 trunk broken? > > i do remember one change for that invalidurlexception > (that we should throw that as an exception instead of just a page expired or > something) > > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner wrote: > >> Using current 1.4 trunk gives me the error >> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: >> Cannot find the rendered page in session [pagemap=nu >> ll,componentPath=1,versionNumber=0] >> org.apache.wicket.protocol.http.request.InvalidUrlException: >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the >> rendered >> page in session [pagemap=null,componentPath=1,versionNumber=0] >> at >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ >> estCycleProcessor.java:250) >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >> at >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 >> ) >> at >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: >> 289) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >> tionFilterChain.java:235) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >> erChain.java:206) >> at >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte >> r.java:96) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica >> tionFilterChain.java:235) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt >> erChain.java:206) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv >> e.java:235) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv >> e.java:191) >> at >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs >> sociationValve.java:190) >> at >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j >> ava:92) >> at >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( >> SecurityContextEstablishmentValve.java:126) >> at >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S >> ecurityContextEstablishmentValve.java:70) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java >> :127) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java >> :102) >> at >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn >> ectionValve.java:158) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. >> java:109) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3 >> 30) >> at >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82 >> 9) >> at >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( >> Http11Protocol.java:598) >> at >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >> at java.lang.Thread.run(Thread.java:619) >> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot >> find the rendered page in session [pagemap=null,componentPath=1,vers >> ionNumber=0] >> at >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ >> estCycleProcessor.java:197) >> ... 25 more >> >> >> On loading a page. Did I miss some big change? >> >> - >> 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 > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: 1.4 trunk broken?
The problem occurs when I klicked around on a page an then deploy a new version of the app. When I klick on a page link now then the error occurs. In former trunk versions and all former wicket version I was redirected to the application's homepage. Stefan -Ursprüngliche Nachricht- Von: Johan Compagner [mailto:jcompag...@gmail.com] Gesendet: Dienstag, 16. Juni 2009 20:19 An: users@wicket.apache.org Betreff: Re: 1.4 trunk broken? i do remember one change for that invalidurlexception (that we should throw that as an exception instead of just a page expired or something) On Tue, Jun 16, 2009 at 18:09, Stefan Lindner wrote: > Using current 1.4 trunk gives me the error > > [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: > Cannot find the rendered page in session [pagemap=nu > ll,componentPath=1,versionNumber=0] > org.apache.wicket.protocol.http.request.InvalidUrlException: > org.apache.wicket.protocol.http.PageExpiredException: Cannot find the > rendered > page in session [pagemap=null,componentPath=1,versionNumber=0] >at > org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ > estCycleProcessor.java:250) >at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >at > org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 > ) >at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: > 289) >at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:235) >at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:206) >at > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte > r.java:96) >at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:235) >at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:206) >at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv > e.java:235) >at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv > e.java:191) >at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs > sociationValve.java:190) >at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j > ava:92) >at > org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( > SecurityContextEstablishmentValve.java:126) >at > org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S > ecurityContextEstablishmentValve.java:70) >at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java > :127) >at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java > :102) >at > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn > ectionValve.java:158) >at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. > java:109) >at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3 > 30) >at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82 > 9) >at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( > Http11Protocol.java:598) >at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >at java.lang.Thread.run(Thread.java:619) > Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot > find the rendered page in session [pagemap=null,componentPath=1,vers > ionNumber=0] >at > org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ > estCycleProcessor.java:197) >... 25 more > > > On loading a page. Did I miss some big change? > > - > 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
Re: 1.4 trunk broken?
i do remember one change for that invalidurlexception (that we should throw that as an exception instead of just a page expired or something) On Tue, Jun 16, 2009 at 18:09, Stefan Lindner wrote: > Using current 1.4 trunk gives me the error > > [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException: > Cannot find the rendered page in session [pagemap=nu > ll,componentPath=1,versionNumber=0] > org.apache.wicket.protocol.http.request.InvalidUrlException: > org.apache.wicket.protocol.http.PageExpiredException: Cannot find the > rendered > page in session [pagemap=null,componentPath=1,versionNumber=0] >at > org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ > estCycleProcessor.java:250) >at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301) >at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419) >at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) >at > org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456 > ) >at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java: > 289) >at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:235) >at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:206) >at > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte > r.java:96) >at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:235) >at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:206) >at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv > e.java:235) >at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv > e.java:191) >at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs > sociationValve.java:190) >at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j > ava:92) >at > org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process( > SecurityContextEstablishmentValve.java:126) >at > org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S > ecurityContextEstablishmentValve.java:70) >at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java > :127) >at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java > :102) >at > org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn > ectionValve.java:158) >at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. > java:109) >at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3 > 30) >at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82 > 9) >at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process( > Http11Protocol.java:598) >at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) >at java.lang.Thread.run(Thread.java:619) > Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot > find the rendered page in session [pagemap=null,componentPath=1,vers > ionNumber=0] >at > org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ > estCycleProcessor.java:197) >... 25 more > > > On loading a page. Did I miss some big change? > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >