Hi all,
I have an unusual requirement for a stateful page that can be accessed
via a static url. To state it another way I would like the same url to
always shows the latest state of a page for that session. For example:
Operations:
1. Initial Render. url = http://ABC/XYZ
2. User changes the
or nabble.com).
Any hints on how to go about this are appreciated.
Ryan
On Mon, Nov 30, 2009 at 6:06 PM, Ryan Crumley crum...@gmail.com wrote:
Hi all,
I have an unusual requirement for a stateful page that can be accessed
via a static url. To state it another way I would like the same url
Matt,
Add this to your WebApplication.init() method:
getResourceSettings().setResourcePollFrequency(null);
Ryan
On Wed, Apr 8, 2009 at 9:33 PM, Matthew Welch matt...@welchkin.net wrote:
I'm experimenting with Wicket inside Google's new Java support for its App
Engine. My simple apps run fine
All,
[If there is a wicketstuff specific mailing list please let me know
and I will be happy to post there (wicketstuff.org is down so its
difficult to find information).]
I am using wicketstuff-merged-resources (3.1-SNAPSHOT) with
wicketstuff-annotation (1.1) and I have found a potential issue
at 9:43 PM, Ryan Crumley crum...@gmail.com wrote:
All,
[If there is a wicketstuff specific mailing list please let me know
and I will be happy to post there (wicketstuff.org is down so its
difficult to find information).]
I am using wicketstuff-merged-resources (3.1-SNAPSHOT
rcrumley
On Fri, May 21, 2010 at 10:04 AM, Jeremy Thomerson
jer...@wickettraining.com wrote:
What's your sf.net ID? I can add you as committer and you can just commit
the patches.
--
Jeremy Thomerson
http://www.wickettraining.com
On Fri, May 21, 2010 at 9:35 AM, Ryan Crumley crum
and superclasses of matching classes would be checked as well for
potentially overridden annotations? Could you provide a test case for your
issues so we can figure out if there isn't a less obtrusive way to fix it?
Cheers, Stefan
On 05/21/2010 04:35 PM, Ryan Crumley wrote:
Thanks Jeremy. I applied
All,
I ran into strange behavior involving wicket ajax updates + chrome + back
button. I am pretty sure the issue is not caused by wicket but I am hoping
the problem might sound familiar to someone and they can point me in the
right direction. The scenario goes like this:
- An ajax request is
What is interesting is this is not a wicket specific issue however it is
more serious when using wicket than other frameworks due to the expired
links causing errors when they reappear.
I created a very simple version of the problem. Chrome and IE8 exhibits the
problem but Firefox and Safari do
3, 2010 at 3:47 PM, Ryan Crumley crum...@gmail.com wrote:
What is interesting is this is not a wicket specific issue however it is
more serious when using wicket than other frameworks due to the expired
links causing errors when they reappear.
I created a very simple version of the problem
I have (I am using MixedParamHybridUrlCodingStrategy) however in this case
the browser is not contacting the server on back button click so the
UrlCodingStrategy does not come into play.
Ryan
On Wed, Oct 6, 2010 at 4:13 PM, mzem...@osc.state.ny.us wrote:
I've had similar issues, have you tried
11 matches
Mail list logo
