Hi,
i posted this underlying text ago, and missed to write in it that i dont use
the default but a BookmarkablePages (with index-strategy) PagingNavigator. I
assuemed that sth. was wrong with this but could now track it down to a
strange wicket behaviour.
If you have a page that has following parts:
head
main
foot
and put there a bookmarkablepagelink in head and foot, no session is issued.
However if you put anything (!) in the middle that needs a session like a
form, usual link or so, then we have following result:
head : BookMarkablePageLink with no session issued
main: any Component with session issued
foot: BookMarkablePageLink with session issued (!)
now the behaviour for the last one seems wrong, as we need no session there
- or is this behaviour wanted that way? Because in that way you cant have
any session-lazy app while using a searchform or any other session using
component... or I'm wrong here?
Best Regards
Korbinian
_____
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Korbinian
Bachl
Gesendet: Freitag, 8. Dezember 2006 18:13
An: [email protected]
Betreff: [Wicket-user] PagingNavigator & (lazy) Session
Hi,
im currently wondering why the PagingNavigator allways issue a session ? (im
on wicket 2.0)
I mean if i create a mainpage and link to 2 subpages all is fine and no
session used. If i embed a PagingNavigator into any page a session will be
created on the moment i access that page, however I didnt see any access to
session in the sourceode so far.
Why is this behaviour ?
Regards
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
