code details -
> >>>>>>>>>> 1) I use Hibernate to fetch 'Account' objects from backend
> >>>>>>>>>> passing on
> >>>>>>>>>> the
> >>>>>>&
Allgo's manager here. Consider me convinced.
This is a very serious issue for us and your help has been invaluable.
I would also like to offer my sincere gratitude.
--
View this message in context:
http://old.nabble.com/Wicket-session-not-threadsafe--tp27074491p27077743.html
Sent fro
>>
> >>>>>>>>> public InboundSession(Request request)
> >>>>>>>>> {
> >>>>>>>>> super(request);
> >>>>>>>>> }
&
gt; the
>>>>>>>>>> username/password.
>>>>>>>>>>
>>>>>>>>>> 2) I use
>>>>>>>>>> MyAppSession extends WebSession
>>>>>>>>>> {
>>>>>>>>
gt;>>>>>>>> accordingly decide whether a user is logged in or not.
>>>>>>>>>
>>>>>>>>> 2) In Login class I pass on the username/password to
>>>>>>>>> HibernateAccountDao
>>>>>&g
nt;
>>>>>>>> }
>>>>>>>>
>>>>>>>> public boolean isUserLoggedIn()
>>>>>>>> {
>>>>>>>> return account !=null;
>>>>>>>> }
>>>>>>&
g completely.
>
> -Original Message-
> From: Soumya [mailto:soumya_...@yahoo.co.in]
> Sent: Friday, January 08, 2010 6:18 AM
> To: users@wicket.apache.org
> Subject: Wicket session not threadsafe?
>
> Hi all,
> I am fairly a newbie in wicket and would appreciate your he
eturn account !=null;
>>>>>>> }
>>>>>>>
>>>>>>> }
>>>>>>>
>>>>>>> So
>>>>>>> effectively I check if
gt;
> -Original Message-
> From: Soumya [mailto:soumya_...@yahoo.co.in]
> Sent: Friday, January 08, 2010 6:18 AM
> To: users@wicket.apache.org
> Subject: Wicket session not threadsafe?
>
> Hi all,
> I am fairly a newbie in wicket and would appreciate your help!
>
t;> in
>>>>>> wicket session.
>>>>>> But I am not sure how these account objects are getting mixed up
>>>>>> between
>>>>>> users.
>>>>>>
>>>>>> Please can someone lead me to the route cause of the issue?
>>>>>>
>>&g
oo.co.in]
Sent: Friday, January 08, 2010 6:18 AM
To: users@wicket.apache.org
Subject: Wicket session not threadsafe?
Hi all,
I am fairly a newbie in wicket and would appreciate your help!
I
have a wicket application which are used on Live by more than 500
users. Now the problem which has arisen is -
;>>>> and fetch the Account object.
>>>>> Account account = accountDao.getAccount(username, password)
>>>>> MyAppSession session = (MyAppSession )getSession();
>>>>> session.setAccount(account);
>>>>> setResponsePage(Home.class
lean isUserLoggedIn()
>>>>>>> {
>>>>>>> return account !=null;
>>>>>>> }
>>>>>>>
>>>>>>> }
>>>>>>>
>>>>>>> So
>>>>>>> effectivel
>>>>>> accordingly decide whether a user is logged in or not.
>>>>>>
>>>>>> 2) In Login class I pass on the username/password to
>>>>>> HibernateAccountDao
>>>>>> and fetch the Account object.
>>>>>> Account account = a
>>>>> and fetch the Account object.
>>>>> Account account = accountDao.getAccount(username, password)
>>>>> MyAppSession session = (MyAppSession )getSession();
>>>>> session.setAccount(account);
>>>>> setResponsePage(Home.
password)
>>>> MyAppSession session = (MyAppSession )getSession();
>>>> session.setAccount(account);
>>>> setResponsePage(Home.class);
>>>>
>>>> So effectively I fetch the accout object using hibernate and store it
>>>> in
>>>> wicket session.
>>>> But I
gt;> Thanks in advance!
>>> SSP
>>>
>>>
>>> The INTERNET now has a personality. YOURS! See your Yahoo! Homepage.
>>> http://in.yahoo.com/
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wic
sonality. YOURS! See your Yahoo! Homepage.
>> http://in.yahoo.com/
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get
A wicket version number would be helpful...
Martijn
On Fri, Jan 8, 2010 at 12:17 PM, Soumya wrote:
> Hi all,
> I am fairly a newbie in wicket and would appreciate your help!
>
> I
> have a wicket application which are used on Live by more than 500
> users. Now the problem which has arisen is - s
Look for static variables on your code too, they may be erroneous sharing
values between session.
On Fri, Jan 8, 2010 at 10:00 AM, Pedro Santos wrote:
> If your servlet container bind an different session for your users
> requests, you get the problem described too. Only one property of your
> s
If your servlet container bind an different session for your users requests,
you get the problem described too. Only one property of your session has
user B values for user A requests? Or the entire session are different?
On Fri, Jan 8, 2010 at 9:52 AM, Pieter Degraeuwe <
pieter.degrae...@systemwo
That's very odd... As I understood, methods on the Session can be called by
several threads. So, Session methods must be thread safe.
Maybe something is wrong with your dao. (Since that wone will be called by
multiple threads a the same time...)
Pieter
On Fri, Jan 8, 2010 at 12:17 PM, Soumya wr
Hi all,
I am fairly a newbie in wicket and would appreciate your help!
I
have a wicket application which are used on Live by more than 500
users. Now the problem which has arisen is - say User A logs on - he is
able to view details of User B. It has happened for different users and
I am trying to
23 matches
Mail list logo
