Re: recuperate session from a directAction
Re: recuperate session from a directAction
- Subject: Re: recuperate session from a directAction
- From: Stephane Guyot <email@hidden>
- Date: Sat, 5 Feb 2005 09:39:40 +0100
Andres,
to come back int the same session for one instance of your
application, you need wosid and woinst.
Are you using URL rewriting ( wosid and woinst in all urls generated by
WO) or are you using storeIDsInCookies ?
In the second case, have a look on the cookies coming in from the
request, check domain, ...
By default, when you call session() inside a WODirectAction, WO does
use the "existing session" if one exists, and creates a new one if not.
( Try existingSession() to avoid session creation)
If WO create a new session, something is missing, wosid or wosint, or
perhaps wosid AND wosint.
To better understand what is missing logs, request headers, uri ...,
and last thing if you are using custom cache page management on
sessions of your application, try call _ensureAwakeInContext, on each
restored page.
HTH,
Stephane
Le 5 févr. 05, à 03:21, Andres Toussaint a écrit :
Hi all:
Is there a way to call a WOComponent with additional parameters in the
queryString from within an embedded application in the browser?
and,
Is there a way to recuperate the session from a DirectAction call that
has a valid wosid?
The base url for the request is generated upon initial build of the
embedded application (that is assembled on the server at runtime), via
the WOActionURL.
The parameters will NOT come from WOForm or variable bindings. These
parameters are generated in runtime by the embedded application, and
thus there is no direct binding to a WOElement.
I have succesfully established this comunication with the server by
using a directAction from within my embedded application, and altough
I provide a WOSID in the query, the DirectAction creates a new session
instead of recuperating the one indicated in the query, and thus the
EOEditingContext is different than the one used in generating the
initial embedded application.
Thanks,
Andres.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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