Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
- Subject: Re: [FIXED] NSMacOSRomanStringEncoding UnsupportedEncodingException
- From: "Cheong Hee (Datasonic)" <email@hidden>
- Date: Wed, 19 Nov 2008 02:53:12 +0800
Will it help if the classpath is changed to point to right java sdk path
after installed?
Most of the other distributions on other platforms realize the world is
bigger than the United States and include the multiplatform JVM support.
For
some reason Microsoft doesn't feel the same need.
I guess it mirrors the built-in support that Macs have for multibyte
languages whereas in the MSFT world you have to install it separately for
IE
to work. In the time of 300gig laptop harddrives and 5 gig OS installs it
seems a waste to worry about another set of deployables that nobody is
ever
going to use.
Dov Rosenberg
On 11/18/08 8:04 AM, "David Avendasora" <email@hidden> wrote:
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
_______________________________________________
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