Re: JQuery contribution question
Hi, On Thu, May 23, 2013 at 11:21 PM, Raul ralva...@netwie.com wrote: Hello, I also need to upgrade the version of jQuery to 1.9.1, I do it with getJavaScriptLibrarySettings (). setJQueryReference (resource), but I have some problems running this version with AjaxEventBehavior. Please start a new thread with more details about the problem. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/JQuery-contribution-question-tp4658999p4659003.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
I found the solution by myself ... mvn clean -DskipTests package does the job on my Windows system -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659009.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs
Hi, I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this (neither does IE always, but almost always it does). Wicket versions are 1.5.8 and 6.7.0 My case is a modal window that contains a panel with Image (org.apache.wicket.markup.html.image.Image) When modal window opens, first request to image's URL is aborted, request's duration 0ms, nothing is transferred to the browser. Second request to the same URL gives status code 200 and browser seems to be happy. meta http-equiv=X-UA-Compatible content=IE=edge does not seem to have any effect and looking from developer tool's console the page mode does not change while rendering. I have not yet had time to make a quick start on this, but only problem I'm facing is that error log level. If the browser aborts any request, what could wicket do about that? Nothing I guess. Should this be debug level? I would like to see real errors but these are filling the logs. -Mikko -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 16. huhtikuuta 2013 14:34 To: users@wicket.apache.org; Martin Dietze Subject: Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs Hi, Does these errors happen in any browser or only in IE ? I remember such problem in IE - the browser renders the page in modeX and during download of the resources switches to modeY, so it closes the opened connections and downloads the resource again. Either modeX or modeY is QuirksMode. The simple solution/workaround is to add meta http-equiv=X-UA-Compatible content=IE=edge to your pages. On Tue, Apr 16, 2013 at 2:27 PM, Martin Dietze d...@fh-wedel.de wrote: After upgrading to Wicket 6, I am getting too many of exceptions like the ones below. They 'happen' either when delivering static contents, like Javascript files (via resource references) or even media contents like images or movies which are written into the response. I've appended two stacktraces, one for each of these two categories. The errors don't seem to occur on ordinary Wicket pages. The application is running in a glassfish container. Having searched google I've found a number of issues, but none of them seemed to match exactly. Thus, does the stuff below look familiar to anyone? Maybe there's a known issue that I'm not yet aware of? In any case I badly need some kind of workaround, since we really cannot roll back the system at this time. Cheers, m. == snip, here's a stacktrace for delivering a Javascript resource = ERROR 2013-04-15T10:45:00 [http-thread-pool-443-(31)] my.company.app.ui.pages.error.ErrorPage [-] [/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/j query/jquery.min-ver-E1288116312E4728F98923C79B034B67.js] An internal server error occured org.apache.wicket.protocol.http.servlet.ResponseIOException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Connection reset by peer at org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(Servl etWebResponse.java:292) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(Heade rBufferingWebResponse.java:99) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.flushResponseAfter Headers(AbstractResource.java:676) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.setResponseHeaders (AbstractResource.java:662) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.respond(AbstractRe source.java:513) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceRequestHandler.resp ond(ResourceRequestHandler.java:75) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceReferenceRequestHan dler.respond(ResourceReferenceRequestHandler.java:108) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(R equestCycle.java:840) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerSt ack.java:64) ~[wicket-request-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java :254) [wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCyc le.java:211) [wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(R equestCycle.java:282) [wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(Wicke tFilter.java:244) [wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilt er.java:188) [wicket-core-6.6.0.jar:6.6.0] at
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
I'm still interested what failures there are on Windows. Most of us develop on Linux/Mac and our CI servers are Linux too. So we have tests failing on Windows from time to time. But usually it is a problem in the tests themselves. On Fri, May 24, 2013 at 10:38 AM, Dirk Forchel dirk.forc...@exedio.comwrote: I found the solution by myself ... mvn clean -DskipTests package does the job on my Windows system -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659009.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs
Hi, On Fri, May 24, 2013 at 10:47 AM, Mikko Pukki mikko.pu...@syncrontech.comwrote: Hi, I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this (neither does IE always, but almost always it does). Wicket versions are 1.5.8 and 6.7.0 My case is a modal window that contains a panel with Image (org.apache.wicket.markup.html.image.Image) When modal window opens, first request to image's URL is aborted, request's duration 0ms, nothing is transferred to the browser. Second request to the same URL gives status code 200 and browser seems to be happy. meta http-equiv=X-UA-Compatible content=IE=edge does not seem to have any effect and looking from developer tool's console the page mode does not change while rendering. I have not yet had time to make a quick start on this, but only problem I'm facing is that error log level. If the browser aborts any request, what could wicket do about that? Nothing I guess. Yes. The server lost its client, the connection is closed, so there is nothing to be done. Should this be debug level? I would like to see real errors but these are filling the logs. I think it is an error. Without this log we cannot even know there is some problem with ModalWindow in IE. The problem is that so far we were not able to identify the problem with IE. Maybe Opera will give better explanation what is the reason for the failure. -Mikko -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 16. huhtikuuta 2013 14:34 To: users@wicket.apache.org; Martin Dietze Subject: Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs Hi, Does these errors happen in any browser or only in IE ? I remember such problem in IE - the browser renders the page in modeX and during download of the resources switches to modeY, so it closes the opened connections and downloads the resource again. Either modeX or modeY is QuirksMode. The simple solution/workaround is to add meta http-equiv=X-UA-Compatible content=IE=edge to your pages. On Tue, Apr 16, 2013 at 2:27 PM, Martin Dietze d...@fh-wedel.de wrote: After upgrading to Wicket 6, I am getting too many of exceptions like the ones below. They 'happen' either when delivering static contents, like Javascript files (via resource references) or even media contents like images or movies which are written into the response. I've appended two stacktraces, one for each of these two categories. The errors don't seem to occur on ordinary Wicket pages. The application is running in a glassfish container. Having searched google I've found a number of issues, but none of them seemed to match exactly. Thus, does the stuff below look familiar to anyone? Maybe there's a known issue that I'm not yet aware of? In any case I badly need some kind of workaround, since we really cannot roll back the system at this time. Cheers, m. == snip, here's a stacktrace for delivering a Javascript resource = ERROR 2013-04-15T10:45:00 [http-thread-pool-443-(31)] my.company.app.ui.pages.error.ErrorPage [-] [/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/j query/jquery.min-ver-E1288116312E4728F98923C79B034B67.js] An internal server error occured org.apache.wicket.protocol.http.servlet.ResponseIOException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Connection reset by peer at org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(Servl etWebResponse.java:292) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(Heade rBufferingWebResponse.java:99) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.flushResponseAfter Headers(AbstractResource.java:676) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.setResponseHeaders (AbstractResource.java:662) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.respond(AbstractRe source.java:513) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceRequestHandler.resp ond(ResourceRequestHandler.java:75) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceReferenceRequestHan dler.respond(ResourceReferenceRequestHandler.java:108) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(R equestCycle.java:840) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerSt ack.java:64) ~[wicket-request-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java :254) [wicket-core-6.6.0.jar:6.6.0] at
Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs
There is an open ticket in our Jira about this problem - https://issues.apache.org/jira/browse/WICKET-3869. It has a quickstart too. You may try to debug it if it reproduces with your setup. On Fri, May 24, 2013 at 11:29 AM, Martin Grigorov mgrigo...@apache.orgwrote: Hi, On Fri, May 24, 2013 at 10:47 AM, Mikko Pukki mikko.pu...@syncrontech.com wrote: Hi, I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this (neither does IE always, but almost always it does). Wicket versions are 1.5.8 and 6.7.0 My case is a modal window that contains a panel with Image (org.apache.wicket.markup.html.image.Image) When modal window opens, first request to image's URL is aborted, request's duration 0ms, nothing is transferred to the browser. Second request to the same URL gives status code 200 and browser seems to be happy. meta http-equiv=X-UA-Compatible content=IE=edge does not seem to have any effect and looking from developer tool's console the page mode does not change while rendering. I have not yet had time to make a quick start on this, but only problem I'm facing is that error log level. If the browser aborts any request, what could wicket do about that? Nothing I guess. Yes. The server lost its client, the connection is closed, so there is nothing to be done. Should this be debug level? I would like to see real errors but these are filling the logs. I think it is an error. Without this log we cannot even know there is some problem with ModalWindow in IE. The problem is that so far we were not able to identify the problem with IE. Maybe Opera will give better explanation what is the reason for the failure. -Mikko -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: 16. huhtikuuta 2013 14:34 To: users@wicket.apache.org; Martin Dietze Subject: Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs Hi, Does these errors happen in any browser or only in IE ? I remember such problem in IE - the browser renders the page in modeX and during download of the resources switches to modeY, so it closes the opened connections and downloads the resource again. Either modeX or modeY is QuirksMode. The simple solution/workaround is to add meta http-equiv=X-UA-Compatible content=IE=edge to your pages. On Tue, Apr 16, 2013 at 2:27 PM, Martin Dietze d...@fh-wedel.de wrote: After upgrading to Wicket 6, I am getting too many of exceptions like the ones below. They 'happen' either when delivering static contents, like Javascript files (via resource references) or even media contents like images or movies which are written into the response. I've appended two stacktraces, one for each of these two categories. The errors don't seem to occur on ordinary Wicket pages. The application is running in a glassfish container. Having searched google I've found a number of issues, but none of them seemed to match exactly. Thus, does the stuff below look familiar to anyone? Maybe there's a known issue that I'm not yet aware of? In any case I badly need some kind of workaround, since we really cannot roll back the system at this time. Cheers, m. == snip, here's a stacktrace for delivering a Javascript resource = ERROR 2013-04-15T10:45:00 [http-thread-pool-443-(31)] my.company.app.ui.pages.error.ErrorPage [-] [/wicket/resource/org.apache.wicket.resource.JQueryResourceReference/j query/jquery.min-ver-E1288116312E4728F98923C79B034B67.js] An internal server error occured org.apache.wicket.protocol.http.servlet.ResponseIOException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Connection reset by peer at org.apache.wicket.protocol.http.servlet.ServletWebResponse.flush(Servl etWebResponse.java:292) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.protocol.http.HeaderBufferingWebResponse.flush(Heade rBufferingWebResponse.java:99) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.flushResponseAfter Headers(AbstractResource.java:676) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.setResponseHeaders (AbstractResource.java:662) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.resource.AbstractResource.respond(AbstractRe source.java:513) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceRequestHandler.resp ond(ResourceRequestHandler.java:75) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.handler.resource.ResourceReferenceRequestHan dler.respond(ResourceReferenceRequestHandler.java:108) ~[wicket-core-6.6.0.jar:6.6.0] at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(R equestCycle.java:840) ~[wicket-core-6.6.0.jar:6.6.0]
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
Hi Martin, I could pinpoint the commit which changed the behavior in our application: git.exe bisect bad 34f43642195058f375d161dbb7cec58b40711423 is the first bad commit commit 34f43642195058f375d161dbb7cec58b40711423 Author: Martin Tzvetanov Grigorov mgrigo...@apache.org Date: Fri Apr 19 12:21:04 2013 +0300 WICKET-5083 Page#isPageStateless() may return wrong value Initialize the page if it is not already when calculating its statefulness :04 04 fc0a2197290a684ebfe415415f1d425fdf43ee2e b723f22ec183769483dfdb9d21b4af0e1b8e5ca1 M wicket-core Success -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659016.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
We will need a quickstart to debug it. With this change the calculation whether a page is stateless or not is postponed to a later phase of the page lifecycle. A page has the pageId (?X) only if it is stateful. On Fri, May 24, 2013 at 1:08 PM, Dirk Forchel dirk.forc...@exedio.comwrote: Hi Martin, I could pinpoint the commit which changed the behavior in our application: git.exe bisect bad 34f43642195058f375d161dbb7cec58b40711423 is the first bad commit commit 34f43642195058f375d161dbb7cec58b40711423 Author: Martin Tzvetanov Grigorov mgrigo...@apache.org Date: Fri Apr 19 12:21:04 2013 +0300 WICKET-5083 Page#isPageStateless() may return wrong value Initialize the page if it is not already when calculating its statefulness :04 04 fc0a2197290a684ebfe415415f1d425fdf43ee2e b723f22ec183769483dfdb9d21b4af0e1b8e5ca1 M wicket-core Success -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659016.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
Here the failure trace: java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at org.apache.wicket.markup.html.PackageResourceTest.packageResourceGuard(PackageResourceTest.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659018.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Problems when upgrading Jquery
Hello, I updated my application to use Jquery 1.9.1, for this I added the following to the Init method of my application class. JavaScriptResourceReference resource = new JavaScriptResourceReference( MyApplication.class, ../../../assets/js/jquery-1.9.1.min.js); getJavaScriptLibrarySettings().setJQueryReference(resource); When it is updated, I have problems, for example AjaxLazyLoadPanel icon, remains loading infinitely. Does anyone knows what could it be? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-when-upgrading-Jquery-tp4659019.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problems when upgrading Jquery
Hi, you should check for JavaScript errors (if any) with a dev tool like FireBug. Hello, I updated my application to use Jquery 1.9.1, for this I added the following to the Init method of my application class. JavaScriptResourceReference resource = new JavaScriptResourceReference( MyApplication.class, ../../../assets/js/jquery-1.9.1.min.js); getJavaScriptLibrarySettings().setJQueryReference(resource); When it is updated, I have problems, for example AjaxLazyLoadPanel icon, remains loading infinitely. Does anyone knows what could it be? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problems-when-upgrading-Jquery-tp4659019.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
I reckon WICKET-5083 is a bugfix for wrong rendered URLs (stateful pages were rendered without a page version number) which in our case was correct but just as a mistake. It seems, that our pages are stateful and therefore get the page version number (page id ?x) attached. As I described above, in our project this results in an error (endless loop) if cookies are not allowed or if a web crawler wants to index the site, because we don't support session IDs in URLs. The only solution I can think of, is to mark these pages as stateless. What is the correct way to do this? A stateless page must be at least bookmarkable and no child component should be stateful. I can remember that the annotation @StatelessComponent in combination with the StatelessChecker and the method call setStatelessHint(true) was necessary to mark a page as being stateless. Is this still necessary? Or what is the preferred way for doing this? As a quick hack I've already changed our render strategy from REDIRECT_TO_BUFFER to REDIRECT_TO_RENDER. In that case no page version id is attached at all. What could be the flaw for using this render strategy as an alternative? Thanks for your helping hand. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659021.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0
On Fri, May 24, 2013 at 3:22 PM, Dirk Forchel dirk.forc...@exedio.comwrote: I reckon WICKET-5083 is a bugfix for wrong rendered URLs (stateful pages were rendered without a page version number) which in our case was correct but just as a mistake. It seems, that our pages are stateful and therefore get the page version number (page id ?x) attached. As I described above, in our project this results in an error (endless loop) if cookies are not allowed or if a web crawler wants to index the site, because we don't support session IDs in URLs. The only solution I can think of, is to mark these pages as stateless. What is the correct way to do this? A stateless page must be at least bookmarkable and no child component should be stateful. I can remember that the annotation @StatelessComponent in combination with the StatelessChecker and the method call setStatelessHint(true) was necessary to mark a page as being stateless. Is this still necessary? Or what is the preferred way for doing this? page.setStatelessHint(false) should be enough to simulate that it is stateless. But check the urls of the links inside the page markup. If there is no ?X then a new page instance will be created to execute the callback method (e.g. onClick()). Since you believed in 6.7.0 that the page is stateless I assume you do not keep any state, so all should be still OK. As a quick hack I've already changed our render strategy from REDIRECT_TO_BUFFER to REDIRECT_TO_RENDER. In that case no page version id is attached at all. What could be the flaw for using this render strategy as an alternative? Check the its javadoc in IRequestCycleSettings Thanks for your helping hand. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659021.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
dynamic form (with list + add/remove)
Hey, I was looking for a good example for creating a dynamic form with a list and add/remove functionality. I looked at the ListView, but this article from Martijn's blog tells to use a RepeatingView http://wicketinaction.com/2008/10/building-a-listeditor-form-component/ this article is from 2008. Is this still the prefered way to do this? Or are there other good examples?
MootipBehaviour Panel Error
http://apache-wicket.1842946.n4.nabble.com/file/n4659025/photo.png - Unable to find the markup for the component. That may be due to transparent containers or components implementing IComponentResolver: [MarkupContainer [Component id = mooTipAjaxPanel]] org.apache.wicket.WicketRuntimeException: Unable to find the markup for the component. That may be due to transparent containers or components implementing IComponentResolver: [MarkupContainer [Component id = mooTipAjaxPanel]] at org.apache.wicket.MarkupFragmentFinder.find(MarkupFragmentFinder.java:125) at org.apache.wicket.Component.locateMarkupStream(Component.java:3918) at org.apache.wicket.Component.renderComponent(Component.java:2621) at org.apache.wicket.ajax.AjaxRequestTarget.respondComponent(AjaxRequestTarget.java:901) Any ideas? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/MootipBehaviour-Panel-Error-tp4659025.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
