×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Buck,

Can you or anyone here tell me how to configure Tomcat to expect the UTF-8
encoding? Can I configure Tomcat for this?  I found the instructions on how
to configure websphere to handle this but I am trying to avoid websphere for
now.

-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Monday, May 13, 2002 4:47 PM
To: web400@midrange.com
Subject: RE: [WEB400] webfacing and tomcat


>I am sure that works for most characters, but I
>don't believe the iSeries natively supports
>UTF-8. It works because UTF-8 duplicates the
>Ascii character set for the first 255? positions,
>and then uses a varying length encoding scheme.
>UTF-8 is the default encoding if nothing is specified
>
>but I would feel more comfortable with ISO-8859-1
>in the United States.

Hi David!
  I suspect this is some artifact of WebFacing SP5, as I didn't encounter
this error on earlier service packs.  Why IBM-generated classes destined for
iSeries would use UTF-8 is beyond me, but it's a hard stop and the only way
around it is to tell WAS that UTF-8 encoding is possible.

I too would be more comfortable with 8859-1, but I don't think I can
influence the way WebFacing generates the classes.
  --buck
_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/web400
or email: WEB400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.