The first thing to do would be to reproduce the issue in a dev environment, then try upgrading that environment to 1.3.7 and see if that solves the problem. There shouldn't be any API breaks in the 1.3 series so this should be a simple POM dependency version update.
It might also be your Hibernate implementation caching and returning the wrong
object as well.
Steve
On 08/01/2010, at 11:21 PM, allgo wrote:
>
> 1.3.0-beta3 actually. Copied it from the Manifest file
>
> Martijn Dashorst wrote:
>>
>> 1.3.0?
>>
>> Martijn
>>
>> On Fri, Jan 8, 2010 at 1:12 PM, allgo <soumya_...@yahoo.co.in> wrote:
>>>
>>> Hi,
>>> The wicket version is 1.3. Sorry should have mentioned that.
>>>
>>> As such the User A, after he logs on is getting assigned the Account
>>> object
>>> of User B. And after soem logs we can see that User B had logged on a
>>> while
>>> before. Hence that Accoutn object was definitely fetched a whiel before.
>>> I
>>> did see a few threads which say Hibernate may eb a culprit but am not
>>> sure
>>> thats the case here.
>>>
>>> Please do let me know if you need any more info.
>>> Thanks,
>>> SSP
>>>
>>> Martijn Dashorst wrote:
>>>>
>>>> A wicket version number would be helpful...
>>>>
>>>> Martijn
>>>>
>>>> On Fri, Jan 8, 2010 at 12:17 PM, Soumya <soumya_...@yahoo.co.in> 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 - 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 dig the real reason.
>>>>>
>>>>> Here is my code details -
>>>>> 1) I use Hibernate to fetch 'Account' objects from backend passing on
>>>>> the
>>>>> username/password.
>>>>>
>>>>> 2) I use
>>>>> MyAppSession extends WebSession
>>>>> {
>>>>> private Account account;
>>>>>
>>>>> public InboundSession(Request request)
>>>>> {
>>>>> super(request);
>>>>> }
>>>>>
>>>>> public void setAccount(Account account)
>>>>> {
>>>>> this.account = account;
>>>>> }
>>>>>
>>>>>
>>>>> public Account getAccount()
>>>>> {
>>>>> return account;
>>>>> }
>>>>>
>>>>> public boolean isUserLoggedIn()
>>>>> {
>>>>> return account !=null;
>>>>> }
>>>>>
>>>>> }
>>>>>
>>>>> So
>>>>> effectively I check if the Account object in session is null or not and
>>>>> 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 = accountDao.getAccount(username, 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 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?
>>>>>
>>>>>
>>>>> 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://wicketinaction.com
>>>> Apache Wicket 1.4 increases type safety for web applications
>>>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Wicket-session-not-threadsafe--tp27074491p27075050.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Wicket-session-not-threadsafe--tp27074491p27075144.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
smime.p7s
Description: S/MIME cryptographic signature
