the classloader will still barf after certain situations i think.
when you add a new property for example and refresh a page, what happens?
a new instance of that component/page is created, but the property's value
is not in the url which might lead to some weird invalid state scenarios.
-igor
On 11/21/06, cowwoc <[EMAIL PROTECTED]> wrote:
Two questions about:
http://howardlewisship.com/blog/2006/10/tapestry-5-screencast-2.html
1) How did they get "instantaneous" page reloads working?
2) How did they get their URLs to remain "nice" even though the
underlying state is changing?
and what is the implications for Wicket? I suspect you guys have
seen
this before. Can you please comment on why Wicket does not do something
similar? Is it something to do with the amount of client-side state they
use?
Thanks,
Gili
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
