I dunno if my ideas are rolling out in the right direction, maybe you
guys who have far more knowledge than me can answer me this:
What about the Application's createSessionForRequest(WOReqeuest
worequest) method? can I check there if the request is an internal or
external and allow the creation of the first session that its never
being terminated??
I dunno im divagating here.
G.
On Sep 24, 2009, at 3:09 PM, Robert Tupelo-Schneck wrote:
On Thu, Sep 24, 2009 at 8:41 AM, Gustavo Pizano
<[email protected]> wrote:
I created a logout WOComponent, which has only "LogOut Successful"
thats it.
in the UserMainPage WOComponent, there is a <WOHyperLink> with an
action
binding to a logOut method, which is doing the follwoing:
...
so when I click the logout link, I go to the LogOut WOComponent,
and I see
the little "Logout successful" , I check the JavaMonitor and still
there is
the session, and if I click the back button I can keep working in the
application as if I didn't ever log out.
Override the Session constructor and terminate() to each log the
sessionID(). Then check the logs to track when sessions begin and
end. That should shed some light.
Robert
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjectspicora%40gmail.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
