Re: Session languages partially ignored with direct actions
Re: Session languages partially ignored with direct actions
- Subject: Re: Session languages partially ignored with direct actions
- From: Alexander Spohr <email@hidden>
- Date: Mon, 12 Jan 2004 21:30:00 +0100
ouch!
forget what i wrote. i was looking in the wrong place.
here's the correction:
some subcomponents use the browser languages and some the session
languages.
yes. WO tries not to touch the session if you're coming in by a direct
action. this is useful if you don't want the accidental creation of a
session. so if you have subcomponents that don't touch the session, it
is not restored until some component needs it. we observed the same
problem.
Well, I've found a very simple workaround. I've added a call to
existingSession in each direct action, and voil`.
public WOActionResults defaultAction ()
{
this.existingSession (); // workaround
return pageWithName ("Main");
}
It's a WebObjects' bug, I think. :)
nope.
each component asks context().hasSession() to determine where the
languages array is lurking around. and hasSession() returns false until
somebody calls for session() or existingSession(). the context does not
read the wosid as long as nobody is interested....
maybe apple should add some switch like
WOApplication.autoRestoreSession(boolean) to always restore the session
if a wosid is in the url.
sorry for the noise.
atze
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.