Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
- Subject: Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
- From: David Avendasora <email@hidden>
- Date: Tue, 18 Nov 2008 08:04:43 -0500
Hey all,
Thanks for all the pointers. All my Component's WOO files did in fact
point to UTF-8, but there must have be things inside WO and/or Wonder
that still use NSMacOSRomanStringEncoding.
I don't know if it is only when deploying to Tomcat on Windows, but
the solution was to uninstall the Windows JRE (and all it's updates)
off the deployment server and install the Multi-Language JDK instead.
Dov suggested this originally but it took me a while to have it sink
in that it was JDK and not JRE. (I hate TLAs!)
Once I did that everything works just fine.
Dave
On Nov 18, 2008, at 7:30 AM, Dov Rosenberg wrote:
We develop exclusively on Macs and have for the past 5 years but
somehow we
had mixed settings in our .woo files as well. We finally converted
them all
to UTF-8 when we moved to Project Wonder. I think the changes probably
occurred as WOLips changed its defaults over the years.
Dov Rosenberg
On 11/18/08 5:19 AM, "Cheong Hee (Datasonic)" <email@hidden
>
wrote:
Hi David
If you could check your Component woo file e.g. Main.woo,
NSMacOSRomanStringEncoding is probably coded. I
I noticed that if the component file is created under Eclipse/
Windows, the
woo file will be as such:
{"WebObjects Release" = "WebObjects 5.0"; encoding = "UTF-8"; }
However, if the component file I imported from Wonder(e.g.
AjaxExampleComponent.woo from WOAjaxExample), the woo file will be
as such:
{
"WebObjects Release" = "WebObjects 5.0";
encoding = NSMacOSRomanStringEncoding;
}
Not sure if this is the cause, just a hint to check. I did encounter
similar NSMacRomanStringEncoding in Windows but can't recall if
resolved.
HTH.
Cheers
Cheong Hee
Message: 4
Date: Mon, 17 Nov 2008 18:17:34 -0500
From: Dov Rosenberg <email@hidden>
Subject: Re: NSMacOSRomanStringEncoding UnsupportedEncodingException
To: Q <email@hidden>, David Avendasora <email@hidden
>
Cc: WebObjects-Dev Mailing List List <webobjects-
email@hidden>
Message-ID: <C54765BE.1C569%email@hidden>
Content-Type: text/plain; charset="us-ascii
You still need to use the localized JDK if you are on Windows
Dov Rosenberg
On 11/17/08 5:26 PM, "Q" <email@hidden> wrote:
Launch tomcat using the JDK instead of the JRE.
On 18/11/2008, at 6:21 AM, David Avendasora wrote:
Okay, I'm stumped.
I'm getting the "java.io.UnsupportedEncodingException:
NSMacOSRomanStringEncoding" error when I load some of my new
Components,
but
only the first time the page is requested after a restart.
I've double-checked all my components properties (and verfied in
the
.woo
files) that the encoding is set to UTF-8 (or in properties that it
inherits
from the container, which is UTF-8).
Everything I've found with on the lists says that these settings
should
fix
this problem, but they don't. I'm running Java 1.6.0_07 on
Windows 2000
Server though Tomcat.
I can't figure out where it's getting something other than UTF-8
in the
first
place.
Dave
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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