@lists.sourceforge.netBetreff: Re: [Wicket-user]
beginners question: wicket and sessions
wicket's session object is stored inside http session. the getters
and setters there are to make your code cleaner then using http session's
map:object-object which is pretty ugly - so instead you use typesafe
On 8/14/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
thx very much - emm, you dont how EJB sessions are working
with wicket ? (do i have to tie the specific stateful bean to the session or
does the container remember itself the bean to the session e.g.for a shopping
cart...)you get a
On 8/14/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
we like dirty() and havent had any complaints so far save this one.
you can always do: MySession { public void sync() { dirty(); } } :)
sure
i can do this... i just meant u usuallydont think about snycronising
whenseeing a dirty()
Hi,
i have a small
problem in understanding the way sessions are used in wicket. Whenever i access
any new wicket app (even HelloWorld) it gives me a SID, so i know i have a (http
servlet) session. However, using the http.session is not the wicket way, and the
wiki just tells:
Custom
wicket's session object is stored inside http session. the getters and setters there are to make your code cleaner then using http session's map:object-object which is pretty ugly - so instead you use typesafe getters and setters. and as johan pointed out whenever you modify wicket's session
