AW: get set attribute wicket session

2010-01-21 Thread Giambalvo, Christian
Hi, with getSession() you will always get the session attached to the current request. So yes it is session specific. Greets chris -Urspr√ľngliche Nachricht- Von: Martin Asenov [mailto:mase...@velti.com] Gesendet: Donnerstag, 21. Januar 2010 16:44 An: users@wicket.apache.org Betreff:

AW: get set attribute wicket session

2010-01-21 Thread Giambalvo, Christian
attribute wicket session Thanks, Chris! Have a nice evening! Cheers, Martin -Original Message- From: Giambalvo, Christian [mailto:christian.giamba...@excelsisnet.com] Sent: Thursday, January 21, 2010 5:46 PM To: users@wicket.apache.org Subject: AW: get set attribute wicket session Hi

Re: AW: get set attribute wicket session

2010-01-21 Thread Joseph Pachod
Giambalvo, Christian wrote: Hi, with getSession() you will always get the session attached to the current request. So yes it is session specific. Greets chris I would add that, in order to save this nasty cast all over the place, you could create your own getMySessionImpl this way : class

RE: AW: get set attribute wicket session

2010-01-21 Thread Martin Asenov
, January 21, 2010 6:26 PM To: users@wicket.apache.org Subject: Re: AW: get set attribute wicket session Giambalvo, Christian wrote: Hi, with getSession() you will always get the session attached to the current request. So yes it is session specific. Greets chris I would add that, in order

AW: AW: get set attribute wicket session

2010-01-21 Thread Giambalvo, Christian
: AW: get set attribute wicket session Giambalvo, Christian wrote: Hi, with getSession() you will always get the session attached to the current request. So yes it is session specific. Greets chris I would add that, in order to save this nasty cast all over the place, you could create your

AW: AW: get set attribute wicket session

2010-01-21 Thread Giambalvo, Christian
, January 21, 2010 6:26 PM To: users@wicket.apache.org Subject: Re: AW: get set attribute wicket session Giambalvo, Christian wrote: Hi, with getSession() you will always get the session attached to the current request. So yes it is session specific. Greets chris I would add that, in order