It should be easy to migrate it to Wicket 6.
What functionality is missing ?
On Tue, Jan 22, 2013 at 12:01 AM, sthomps stho...@gmail.com wrote:
Yeah I took a quick look at that project but it appears to be abandoned and
only supports links.
--
View this message in context:
Just reading through the description - the components only included
StatelessLink and a StatelessAjaxFallbackLink
Browsing through the source code, it appears that there are stateless
behaviors that can be added to other Ajax components.
Best thing to do is to test it out :)
--
View this
Hi,
We have created similar workarounds in 1.4 as you have. These are now
in Wicket 6. I am still trying to find opportunities for improvements
in 6. Please consider Mounted bookmarkable Page not recreated on
Session Expiry
https://issues.apache.org/jira/browse/WICKET-4997
Perhaps you want to
For Wicket 6 I have a workaround shown in Mounted bookmarkable Page
not recreated on Session Expiry
https://issues.apache.org/jira/browse/WICKET-4997
The other workarounds I made were in 1.4. Wicket 6 solves these
non-AJAX issues out of the box. Please follow the recent thread
Passing IModel in
Why don't you just keep the session alive as long as the user has an
ajax page open? You can easily do this by letting the page do a timed
ajax call to the server every x minutes, where x is slightly less than
your session timeout.
On Mon, Jan 21, 2013, at 17:56, sthomps wrote:
I'm currently in
It's just not efficient.
We have users that will let their pages sit for hours before they come back
to them.
I would rather have these sessions/memory be reclaimed, and if a user has a
stale page, the Ajax action continues on as normal.
We also have a sudo portal that contains applications
How does Tapestry solve the problem explained in the comments you pasted ?
On Mon, Jan 21, 2013 at 8:15 PM, sthomps stho...@gmail.com wrote:
It's just not efficient.
We have users that will let their pages sit for hours before they come back
to them.
I would rather have these
You can read the Tapestry response a
href=http://tapestry.1045711.n5.nabble.com/Session-Expiration-Ajax-td5719213.html;here.
Essentially there are no PageMaps/versions per users session.
--
View this message in context:
Well, I'll need some more technical details about Tapestry internals to
understand what they do.
You can check https://github.com/jolira/wicket-stateless - it provides few
Ajax behaviors and components which are stateless, i.e. they re-create the
whole page for each request.
I think this is what
Speaking of this, I had the same issue recently.
I wished for stateless pages but as I didn't know, I opted for
keep-alive ajax requests.
Is there some article, blog, tutorial or whatever on how to keep pages
stateless?
I know that if a page is bookmarkable and doesn't contain any
10 matches
Mail list logo
