On 13-Jun-07, at 1:58 PM, Ralf Schuchardt wrote:
Am 12.06.2007 um 18:57 schrieb Rick Innis:
From some previous searching I believe this may be connected to
the fact that the applications affected are both localized, so the
template it's looking exists in Contents/Resources/
{French,English}.lproj but not in Contents/Resources.
I have the same issue in one of my apps. It may happen when the
browser language detection does not return not a valid language set
(WORequest.browserLanguages).
There is the special language "Nonlocalized". According to the
NSBundle documentation all Resources in this language get mapped to
the Resources directory itself. You could put a fallback page here.
I ended up symlinking Contents/Resources/English.lproj/*.wo to
Contents/Resources, which appears to work. However, I remain baffled
as to why this is necessary. WORequest.browserLanguages looks OK - it
prints as ("English","English") - but using this as input to
session.setLanguages() didn't seem to matter a set of foetid dingoes
kidneys.
The application basically consists of a static page and a few forms,
available in both English and French, and each page is invoked via a
method on DirectAction. defaultAction() invokes englishAction(), and
frenchAction exists to allow switching from the English page to
French one. Interestingly, calling <application-url>/1/wa/
frenchAction actually *does* work as expected; calling <application-
url>/1/wa/englishAction does *not*.
I did track down the threads "A problem with localization" and
"Strange WebObjects Localization, need help" from a couple of years
ago in the list archives, but none of what was suggested there seemed
to help this situation either.
Since the workaround seems to work I'm not desperate for a fix, but I
remain baffled as to why it's necessary. For further context and
bafflement, it runs fine on my dev machines (both my G5 and my
MacBook); the problem only manifests on the production server (to
be), which is an Intel Xserve with a shiny fresh new install of Tiger
Server, complete with all required patches. (The only difference I
can think of is that the Xserve have Java 1.4.2 while the dev
machines have 1.5, but I can't see that being a factor. Still, I
suppose it's worth exploring...)
--Rick.
_______________________________________________
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]
