[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482219#comment-16482219
]
KAHA commented on WICKET-6452:
--
Hi,
Currently, our cache is setting for 5 pages stored in memory and 200 MB of disk
cache. I Think than 200 MB is per sesion, so I hope it is enough. Of course, we
can try to increase it, but I thinkg it will be with no result, because the
cache on HDD has real size about 20MB in this case.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
>Priority: Major
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WICKET-6545) Argument 'markup' may not be null.
[ https://issues.apache.org/jira/browse/WICKET-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415247#comment-16415247 ] KAHA commented on WICKET-6545: -- Ok, than kyou, I will test it with next comming M10 :) (or on snapshot version) > Argument 'markup' may not be null. > -- > > Key: WICKET-6545 > URL: https://issues.apache.org/jira/browse/WICKET-6545 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 8.0.0-M9 >Reporter: KAHA >Assignee: Sven Meier >Priority: Critical > > After switch in maven POM from version M8 to M9 wicket has satred reporting > problem > "Argument 'markup' may not be null." during render component which is > descendant of MarkupContainer. > > In version 8.0.0-M8 was everythig allright, but in version 8.0.0-M9, there is > error > Message: Argument 'markup' may not be null. > Root cause: > java.lang.IllegalArgumentException: Argument 'markup' may not be null. > at org.apache.wicket.util.lang.Args.notNull(Args.java:41) > at org.apache.wicket.markup.MarkupStream.(MarkupStream.java:65) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.renderHeadForInnerSiblings(TransparentWebMarkupContainer.java:134) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.internalRenderHead(TransparentWebMarkupContainer.java:89) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy$1.component(ChildFirstHeaderRenderStrategy.java:85) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:96) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:51) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderChildHeaders(ChildFirstHeaderRenderStrategy.java:94) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderHeader(ChildFirstHeaderRenderStrategy.java:57) > at > org.apache.wicket.page.PartialPageUpdate.writeHeaderContribution(PartialPageUpdate.java:551) > at > org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(XmlPartialPageUpdate.java:75) > at > org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:262) > at > org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162) > at eu.abra.web.base.AjaxRequestHandler.respond(AjaxRequestHandler.java:343) > at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) > at > org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) > at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) > at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) > at > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) > at > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) > at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) > at > org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:119) > at > org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96) > at > org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317) > at > org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160) > at > org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199) > at > org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107) > at > org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:63) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WICKET-6545) Argument 'markup' may not be null.
[
https://issues.apache.org/jira/browse/WICKET-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415126#comment-16415126
]
KAHA commented on WICKET-6545:
--
Ok I put it into our POM and which version number (od id) should I put as
wicket versin ? Which idenifier is for latest snapshot ?
org.apache.wicket
wicket-core
${wicket.version}
> Argument 'markup' may not be null.
> --
>
> Key: WICKET-6545
> URL: https://issues.apache.org/jira/browse/WICKET-6545
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M9
>Reporter: KAHA
>Assignee: Andrea Del Bene
>Priority: Critical
>
> After switch in maven POM from version M8 to M9 wicket has satred reporting
> problem
> "Argument 'markup' may not be null." during render component which is
> descendant of MarkupContainer.
>
> In version 8.0.0-M8 was everythig allright, but in version 8.0.0-M9, there is
> error
> Message: Argument 'markup' may not be null.
> Root cause:
> java.lang.IllegalArgumentException: Argument 'markup' may not be null.
> at org.apache.wicket.util.lang.Args.notNull(Args.java:41)
> at org.apache.wicket.markup.MarkupStream.(MarkupStream.java:65)
> at
> org.apache.wicket.markup.html.TransparentWebMarkupContainer.renderHeadForInnerSiblings(TransparentWebMarkupContainer.java:134)
> at
> org.apache.wicket.markup.html.TransparentWebMarkupContainer.internalRenderHead(TransparentWebMarkupContainer.java:89)
> at
> org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy$1.component(ChildFirstHeaderRenderStrategy.java:85)
> at
> org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:96)
> at
> org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87)
> at
> org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87)
> at
> org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:51)
> at
> org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderChildHeaders(ChildFirstHeaderRenderStrategy.java:94)
> at
> org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderHeader(ChildFirstHeaderRenderStrategy.java:57)
> at
> org.apache.wicket.page.PartialPageUpdate.writeHeaderContribution(PartialPageUpdate.java:551)
> at
> org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(XmlPartialPageUpdate.java:75)
> at
> org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:262)
> at
> org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162)
> at eu.abra.web.base.AjaxRequestHandler.respond(AjaxRequestHandler.java:343)
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912)
> at
> org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65)
> at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286)
> at
> org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:119)
> at
> org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96)
> at
> org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317)
> at
> org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160)
> at
> org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199)
> at
> org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107)
> at
> org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:63)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WICKET-6545) Argument 'markup' may not be null.
[ https://issues.apache.org/jira/browse/WICKET-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415094#comment-16415094 ] KAHA commented on WICKET-6545: -- Ok I can test it, but you have to tell me how can I use latest snapshot via MAVEN. > Argument 'markup' may not be null. > -- > > Key: WICKET-6545 > URL: https://issues.apache.org/jira/browse/WICKET-6545 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 8.0.0-M9 >Reporter: KAHA >Assignee: Andrea Del Bene >Priority: Critical > > After switch in maven POM from version M8 to M9 wicket has satred reporting > problem > "Argument 'markup' may not be null." during render component which is > descendant of MarkupContainer. > > In version 8.0.0-M8 was everythig allright, but in version 8.0.0-M9, there is > error > Message: Argument 'markup' may not be null. > Root cause: > java.lang.IllegalArgumentException: Argument 'markup' may not be null. > at org.apache.wicket.util.lang.Args.notNull(Args.java:41) > at org.apache.wicket.markup.MarkupStream.(MarkupStream.java:65) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.renderHeadForInnerSiblings(TransparentWebMarkupContainer.java:134) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.internalRenderHead(TransparentWebMarkupContainer.java:89) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy$1.component(ChildFirstHeaderRenderStrategy.java:85) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:96) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:51) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderChildHeaders(ChildFirstHeaderRenderStrategy.java:94) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderHeader(ChildFirstHeaderRenderStrategy.java:57) > at > org.apache.wicket.page.PartialPageUpdate.writeHeaderContribution(PartialPageUpdate.java:551) > at > org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(XmlPartialPageUpdate.java:75) > at > org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:262) > at > org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162) > at eu.abra.web.base.AjaxRequestHandler.respond(AjaxRequestHandler.java:343) > at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) > at > org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) > at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) > at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) > at > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) > at > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) > at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) > at > org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:119) > at > org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96) > at > org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317) > at > org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160) > at > org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199) > at > org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107) > at > org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:63) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WICKET-6545) Argument 'markup' may not be null.
[ https://issues.apache.org/jira/browse/WICKET-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413028#comment-16413028 ] KAHA commented on WICKET-6545: -- Probably not, becasue the calss is part of very complex project .. But I found the problem is that the rendering has changed. During rendering of the TransparentWebMarkupContainer component in the internalReanderHead method in M8, the isParentRendering method returns true. On other hand same method return false in M9. This leads to differences in behavior. The actual status is right in M8. Parent is also rendered. the isParentRendering method calls parent.isRendering () and isRendering reads in M8 version, FLAG_RENDERING, whereas in M9 RFLAG_RENDERING. There may be something wrong about these changes. > Argument 'markup' may not be null. > -- > > Key: WICKET-6545 > URL: https://issues.apache.org/jira/browse/WICKET-6545 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 8.0.0-M9 >Reporter: KAHA >Priority: Critical > > After switch in maven POM from version M8 to M9 wicket has satred reporting > problem > "Argument 'markup' may not be null." during render component which is > descendant of MarkupContainer. > > In version 8.0.0-M8 was everythig allright, but in version 8.0.0-M9, there is > error > Message: Argument 'markup' may not be null. > Root cause: > java.lang.IllegalArgumentException: Argument 'markup' may not be null. > at org.apache.wicket.util.lang.Args.notNull(Args.java:41) > at org.apache.wicket.markup.MarkupStream.(MarkupStream.java:65) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.renderHeadForInnerSiblings(TransparentWebMarkupContainer.java:134) > at > org.apache.wicket.markup.html.TransparentWebMarkupContainer.internalRenderHead(TransparentWebMarkupContainer.java:89) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy$1.component(ChildFirstHeaderRenderStrategy.java:85) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:96) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) > at > org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:51) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderChildHeaders(ChildFirstHeaderRenderStrategy.java:94) > at > org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderHeader(ChildFirstHeaderRenderStrategy.java:57) > at > org.apache.wicket.page.PartialPageUpdate.writeHeaderContribution(PartialPageUpdate.java:551) > at > org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(XmlPartialPageUpdate.java:75) > at > org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:262) > at > org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162) > at eu.abra.web.base.AjaxRequestHandler.respond(AjaxRequestHandler.java:343) > at > org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) > at > org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) > at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) > at > org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) > at > org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) > at > org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) > at > org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) > at > org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) > at > org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:119) > at > org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96) > at > org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317) > at > org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160) > at > org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199) > at > org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107) > at > org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:63) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WICKET-6545) Argument 'markup' may not be null.
KAHA created WICKET-6545: Summary: Argument 'markup' may not be null. Key: WICKET-6545 URL: https://issues.apache.org/jira/browse/WICKET-6545 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 8.0.0-M9 Reporter: KAHA After switch in maven POM from version M8 to M9 wicket has satred reporting problem "Argument 'markup' may not be null." during render component which is descendant of MarkupContainer. In version 8.0.0-M8 was everythig allright, but in version 8.0.0-M9, there is error Message: Argument 'markup' may not be null. Root cause: java.lang.IllegalArgumentException: Argument 'markup' may not be null. at org.apache.wicket.util.lang.Args.notNull(Args.java:41) at org.apache.wicket.markup.MarkupStream.(MarkupStream.java:65) at org.apache.wicket.markup.html.TransparentWebMarkupContainer.renderHeadForInnerSiblings(TransparentWebMarkupContainer.java:134) at org.apache.wicket.markup.html.TransparentWebMarkupContainer.internalRenderHead(TransparentWebMarkupContainer.java:89) at org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy$1.component(ChildFirstHeaderRenderStrategy.java:85) at org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:96) at org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) at org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:87) at org.apache.wicket.markup.renderStrategy.DeepChildFirstVisitor.visit(DeepChildFirstVisitor.java:51) at org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderChildHeaders(ChildFirstHeaderRenderStrategy.java:94) at org.apache.wicket.markup.renderStrategy.ChildFirstHeaderRenderStrategy.renderHeader(ChildFirstHeaderRenderStrategy.java:57) at org.apache.wicket.page.PartialPageUpdate.writeHeaderContribution(PartialPageUpdate.java:551) at org.apache.wicket.page.XmlPartialPageUpdate.writeComponent(XmlPartialPageUpdate.java:75) at org.apache.wicket.page.PartialPageUpdate.writeComponents(PartialPageUpdate.java:262) at org.apache.wicket.page.PartialPageUpdate.writeTo(PartialPageUpdate.java:162) at eu.abra.web.base.AjaxRequestHandler.respond(AjaxRequestHandler.java:343) at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:912) at org.apache.wicket.request.RequestHandlerExecutor.execute(RequestHandlerExecutor.java:65) at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:283) at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:253) at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:262) at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:204) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:286) at org.atmosphere.util.AtmosphereFilterChain.doFilter(AtmosphereFilterChain.java:119) at org.atmosphere.util.AtmosphereFilterChain.invokeFilterChain(AtmosphereFilterChain.java:96) at org.atmosphere.handler.ReflectorServletProcessor$FilterChainServletWrapper.service(ReflectorServletProcessor.java:317) at org.atmosphere.handler.ReflectorServletProcessor.onRequest(ReflectorServletProcessor.java:160) at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:199) at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:107) at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:63) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153547#comment-16153547
]
KAHA commented on WICKET-6452:
--
Now we are using wicket 7.8.0
yes you are right it is similar as WICKET-4733. But 4733 was about
StalePageExceptions. Here is no exception. Here is problem with serialization
and deserialization page ..
Store Page 107 on session node01afimri2ixqlb14azexfgs28gg0//PAGE IS
SERIALIZED
Store Page 108 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 107 for session node01afimri2ixqlb14azexfgs28gg0 result null
//DESERIALIZATION RETURN NULL and this is reason to create new page instance
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Attachment: (was: test.zip)
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Attachment: test.zip
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Attachment: test.zip
Simple test project
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153538#comment-16153538
]
KAHA commented on WICKET-6452:
--
Ok, i have made new demo project (in zip file) . I have tested it on version
8.0.0-M6. here is log file where you can see that page 107 was stored, but
loading page 107 from store return null and new page is created and rendered
again ...
Store Page 107 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 108 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 107 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 109 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 109 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 108 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 110 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 110 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 109 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 111 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 111 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 110 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 112 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 112 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 111 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 113 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 113 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 112 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 114 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 114 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 113 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 115 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 115 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 114 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 116 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 116 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 115 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 117 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 117 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 116 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 118 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 118 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 118 on session node01afimri2ixqlb14azexfgs28gg0
Get Page 117 for session node01afimri2ixqlb14azexfgs28gg0 result null
Store Page 119 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 119 on session node01afimri2ixqlb14azexfgs28gg0
Store Page 119 on session node01afimri2ixqlb14azexfgs28gg0
It looks that this behavior is better on version 8.0.0-M7. But still on version
8.0.0-M7 I am able to reproduce this error on our project. But our project is
much much complicated that this simple example.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov, test.zip
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153258#comment-16153258
]
KAHA commented on WICKET-6452:
--
I am not sure, that I understand you.
I have made a new directory "D:\WicketTest". I have opened power shell in
Windows ..
I have moved into new directory
D:
cd WicketTest
and now I ran command which has been generated by the Quick Start Wizard and I
got this error
I am sure that I followed instruction from 1 to 5 on Quick Start Wizard page
I have also tried to register new archetype in eclipse and make new project
form eclipse, but i got other error
"Can't resolve Archetype org.apache.wicket:wicket-archetype-quickstart:8.0.0-M6
org.eclipse.core.runtime.CoreException: Could not resolve artifact
org.apache.wicket:wicket-archetype-quickstart:pom:8.0.0-M6"
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153238#comment-16153238
]
KAHA commented on WICKET-6452:
--
Yours DEMO generator (http://wicket.apache.org/start/quickstart.html) doesnot
works with maven 3.3.9
[INFO] Scanning for projects...
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 0.064 s
[INFO] Finished at: 2017-09-05T09:35:45+02:00
[INFO] Final Memory: 13M/368M
[INFO]
[ERROR] The goal you specified requires a project to execute but there is no
POM in this directory (D:\WicketTest). Please verify you invoked Maven from the
correct directory. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
I will try to make demo "by foot" ..
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is created many
> times repeatly.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128465#comment-16128465
]
KAHA commented on WICKET-6452:
--
It looks like that problem is not in PageProvider.getPageInstance() because
there is a code which after deserialization when provision is null call
Provision().resolve(); and this method try to get page from store BUT ...
I have done a little hack ..
I have done in my WabApplication class in method
protected void internalInit() {
.
setPageManagerProvider(new DefaultPageManagerProvider(this) {
@Override
protected IPageStore newPageStore(IDataStore dataStore)
{
int inmemoryCacheSize =
getStoreSettings().getInmemoryCacheSize();
ISerializer pageSerializer =
application.getFrameworkSettings().getSerializer();
return new DefaultPageStore(pageSerializer,
dataStore, inmemoryCacheSize) {
@Override
public IManageablePage getPage(String
sessionId, int pageId) {
IManageablePage page =
super.getPage(sessionId, pageId);
LOG.warn("Get Page "+pageId+"
for session "+sessionId+" result "+page);
return page;
}
@Override
public void storePage(String sessionId,
IManageablePage page) {
super.storePage(sessionId,
page);
LOG.warn("Store Page
"+page.getPageId()+ " on session "+sessionId);
}
};
}
It is same PageManagerProvider as it is there by default, only including LOG
whihe stroing page and geting page. And here is the problem .. Here is LOG. As
you can see, for example PAGE with id 3 was stored, but Get page with id 3 on
same session return NULL.
2017-08-16 09:24:57.569 WARN - AbraWebApplication - Store Page 1 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.614 WARN - AbraWebApplication - Store Page 4 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.645 WARN - AbraWebApplication - Store Page 3 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.686 WARN - AbraWebApplication - Store Page 5 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.718 WARN - AbraWebApplication - Store Page 6 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.730 WARN - AbraWebApplication - Get Page 3 for
session yw58aresd9pb25i3n462j7k9 result null
2017-08-16 09:24:57.761 WARN - AbraWebApplication - Store Page 2 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.793 WARN - AbraWebApplication - Store Page 3 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.833 WARN - AbraWebApplication - Store Page 4 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.868 WARN - AbraWebApplication - Store Page 6 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.910 WARN - AbraWebApplication - Store Page 5 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.944 WARN - AbraWebApplication - Store Page 2 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:57.978 WARN - AbraWebApplication - Store Page 3 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.010 WARN - AbraWebApplication - Store Page 6 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.011 WARN - AbraWebApplication - Get Page 6 for
session yw58aresd9pb25i3n462j7k9 result [Page class =
eu.abra.app.igate.runtime.DynamicPage, id = 6, render count = 1]
2017-08-16 09:24:58.047 WARN - AbraWebApplication - Store Page 2 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.102 WARN - AbraWebApplication - Store Page 7 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.126 WARN - AbraWebApplication - Get Page 2 for
session yw58aresd9pb25i3n462j7k9 result [Page class =
eu.abra.app.igate.runtime.DynamicPage, id = 2, render count = 1]
2017-08-16 09:24:58.168 WARN - AbraWebApplication - Store Page 7 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.213 WARN - AbraWebApplication - Store Page 5 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.249 WARN - AbraWebApplication - Store Page 4 on
session yw58aresd9pb25i3n462j7k9
2017-08-16 09:24:58.277 WARN - AbraWebApplication - Store Page 5 on
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that problem is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is created many
times repeatly.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that problem is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInst
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that problem is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that problem is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() lo
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> {{if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> }}
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageIn
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> {{
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> }}
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.g
[jira] [Commented] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127131#comment-16127131
]
KAHA commented on WICKET-6452:
--
I have uploaded video in two formats because I am not sure which format will
work for you
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is rendered many
> times.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Attachment: ABRA BI - Google Chrome 15.08.2017 13_33_45_x264.mov
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4, ABRA BI
> - Google Chrome 15.08.2017 13_33_45_x264.mov
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage();
> and In Provision class method getPage looks like this
> if (page == null && doesProvideNewPage())
> {
> page = getPageSource().newPageInstance(pageClass,
> pageParameters);
> }
> return page;
> if the page is null, method does not try to load page stored on the disk, but
> imediatly creates a new instance and this is why same page is rendered many
> times.
> But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
KAHA created WICKET-6452:
Summary: Problem while multiple opening same page in WICkET
8.0.0-M6
Key: WICKET-6452
URL: https://issues.apache.org/jira/browse/WICKET-6452
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 8.0.0-M6
Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
(build 1.8.0_131-b11)
Reporter: KAHA
Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
{{if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
}}
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (WICKET-6452) Problem while multiple opening same page in WICkET 8.0.0-M6
[
https://issues.apache.org/jira/browse/WICKET-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
KAHA updated WICKET-6452:
-
Description:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
was:
As you can see on the video, there is a problem when I multiple open same page.
Each one page is rendered again and again and again (you can see it on rapidly
increasing page number). There were no problem with same excercise on Wicket 7.
I think that proble is in method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
Wicket 7 there was
{{if (pageInstance == null)
{
resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
if (pageInstance == null)
{
throw new PageExpiredException("Page with id '" + pageId + "'
has expired.");
}
}
return pageInstance;
}}
If pageInstance is null, method resolvePageInstance is called and
resolvePageInstance first trying to load page stored on disk (stored thanks
Serialization) and it will success. If there is no page stored on disk with
this pageID, than getPageSource().newPageInstance( ... is called to create new
page instance.
On other hand on the new wicket 8 same method
org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
like this
return getProvision().getPage();
and In Provision class method getPage looks like this
{{if (page == null && doesProvideNewPage())
{
page = getPageSource().newPageInstance(pageClass,
pageParameters);
}
return page;
}}
if the page is null, method does not try to load page stored on the disk, but
imediatly creates a new instance and this is why same page is rendered many
times.
But it is only my guess.
> Problem while multiple opening same page in WICkET 8.0.0-M6
> ---
>
> Key: WICKET-6452
> URL: https://issues.apache.org/jira/browse/WICKET-6452
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 8.0.0-M6
> Environment: Windows 10 64bit CZ Java(TM) SE Runtime Environment
> (build 1.8.0_131-b11)
>Reporter: KAHA
> Attachments: ABRA BI - Google Chrome 15.08.2017 13_33_45.mp4
>
>
> As you can see on the video, there is a problem when I multiple open same
> page. Each one page is rendered again and again and again (you can see it on
> rapidly increasing page number). There were no problem with same excercise on
> Wicket 7.
> I think that proble is in method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance(). In
> Wicket 7 there was
> if (pageInstance == null)
> {
> resolvePageInstance(pageId, pageClass, pageParameters, renderCount);
> if (pageInstance == null)
> {
> throw new PageExpiredException("Page with id '" + pageId + "'
> has expired.");
> }
> }
> return pageInstance;
> If pageInstance is null, method resolvePageInstance is called and
> resolvePageInstance first trying to load page stored on disk (stored thanks
> Serialization) and it will success. If there is no page stored on disk with
> this pageID, than getPageSource().newPageInstance( ... is called to create
> new page instance.
> On other hand on the new wicket 8 same method
> org.apache.wicket.core.request.handler.PageProvider.getPageInstance() looks
> like this
> return getProvision().getPage
[jira] [Created] (WICKET-6359) The type org.apache.wicket.ajax.json.JSONObject cannot be resolved. It is indirectly referenced from required .class files
KAHA created WICKET-6359: Summary: The type org.apache.wicket.ajax.json.JSONObject cannot be resolved. It is indirectly referenced from required .class files Key: WICKET-6359 URL: https://issues.apache.org/jira/browse/WICKET-6359 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 8.0.0-M5 Environment: Eclipse Neon.3 WINDOWS 10 64bit CZ, JAVA 8 Reporter: KAHA Assignee: Emond Papegaaij We are using Wicket with apmospeher. In combination Wicket 8.0.0-M5 and wicket-atmosphere 0.25 (from maven groupid=org.apache.wicket.experimental.wicket8, artifactId=wicket-atmosphere version 0.25) there is a problem "The type org.apache.wicket.ajax.json.JSONObject cannot be resolved. It is indirectly referenced from required .class files". It is probably in class AtmosphereParameters. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
