Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

wosid != session().sessionID()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

wosid != session().sessionID()

Subject: wosid != session().sessionID()
From: "Ricardo J. Parada" <email@hidden>
Date: Tue, 28 Oct 2008 20:37:09 -0400

I have a direct action that sometimes it gets a null pointer exception because some of the information previously stored in the session is no longer there and my code assumes it is there. Anyways, digging a little bit more I found out that the reason is doesn't find the information stored in the session is because the session() method is not returning the original session corresponding to the wosid in the URL. I made my direct action log the wosid from the URL and session().sessionID() and they are different:

wosid = iLdoMvh8zYtFsNsph9lltg
session().sessionID() = Hh5Qoar5sRzlXzwDnvBh0w

Anyways, does any body have any advise as to why this is happening? If the original session expired, would then session() return a new session?

Thanks,
Ricardo Parada

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: wosid != session().sessionID()
From: Faizel Dakri <email@hidden>
Re: wosid != session().sessionID()
From: Chuck Hill <email@hidden>


Prev by Date:
Object Store Coordinator and User Info – Is this Dangerous?

Next by Date:
Re: Object Store Coordinator and User Info – Is this Dangerous?

Previous by thread:
Re: Object Store Coordinator and User Info – Is this Dangerous?

Next by thread:
Re: wosid != session().sessionID()

Index(es):

Date
Thread