Re: Localization problem, hello world too [solved]
Re: Localization problem, hello world too [solved]
- Subject: Re: Localization problem, hello world too [solved]
- From: Ramsey Lee Gurley <email@hidden>
- Date: Tue, 02 Dec 2008 17:55:41 -0500
On Dec 2, 2008, at 2:53 AM, Anjo Krank wrote:
Am 02.12.2008 um 08:04 schrieb Anjo Krank:
If it doesn't, rewrite the method so it re-orders the nsarray so
that it still has all items from _expectedLanguages, but the ones
from nsarray come first and in order and post a patch.
I checked in an (untested) interim patch. See if the problem persists.
Cheers, Anjo
Nice patch :-) Oh, and for the record, what I was saying earlier
about needing to return something from session languages() is complete
garbage... I see you've already taken care of that in ERXSession's
setLanguage(). The problem here was my test app was returning null
from the updateLanguage() action instead of a page. [Are you listening
to this Mike? :-) ] I think this must be different from Mike and
Chuck's debate though, because even returning context().page() causes
the contents of the current page object to be re-rendered instead of
refreshing the localized component. I actually needed to do
public WOActionResults updateLang() {
return
WOApplication.application().pageWithName(context().page().name(),
context());
}
to get the right localized page component when changing languages.
Perhaps there's another way to invalidate the page and cause the whole
thing to refresh, but I'm satisfied with that for now...
Ramsey
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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