Re: Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
Hello, Yes, I did, realizing that it's a bit of a coarse solution. As it happens, my application main function is to execute scripts for automated deployment on a WebSphere platform, so users work with a JEE-application they select from a wicket Ajax-textfield with application build versions that's connected with our Nexus repository (that at it's turn is populated with Maven-builds by Hudson). So, these users want to download builds, installation manuals, reports, and the like for inspection and reference. As a result, /any/ download is dynamically created at runtime, so there is no wish for caching, on the contrary, and it's not to be expected that it will be. Nevertheless, I will delve into the org.apache.wicket.request.resource.AbstractResource.ResourceResponse#setCacheDuration, because I like fitting solutions, and not over-sized ones: I tend to believe that that is what you are hinting at in your reply. I just have to figure out how the setCacheDuration can be applied to the AbstractResourceStreams that I use. Many thanks! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4077423.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: Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
Hi, On Sat, Nov 12, 2011 at 7:15 PM, hfriederichs h.friederi...@ohra.nl wrote: I solved the issue by many trial and error sessions. Maybe I can spare someone else this ordeal. In Firefox an Chrome it now works as in IE, by adding this statement in the init() of my WicketApplication: getResourceSettings().setDefaultCacheDuration(Duration.NONE); So you basically disabled the caching for *all* resources just because you need to disable the caching for one resource. See org.apache.wicket.request.resource.AbstractResource.ResourceResponse.getCacheDuration() Regards, Hans Friederichs -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4034881.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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
I solved the issue by many trial and error sessions. Maybe I can spare someone else this ordeal. In Firefox an Chrome it now works as in IE, by adding this statement in the init() of my WicketApplication: getResourceSettings().setDefaultCacheDuration(Duration.NONE); Regards, Hans Friederichs -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4034881.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: Migrating a ResourceStreamRequestTarget to a ResourceStreamRequestHandler (2)
Made a quick start, but couldn't reproduce the issue, it worked in FireFox... Be it on a Jetty-server, and I have to cope with WebSphere... Well, I'll strip my application down to the essentials that I have in the quick start, and then build up one by one, I guess. Many thanks, so far! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-2-tp4019661p4020304.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
