PROTECTED]
Sent: Wednesday, July 25, 2007 7:47 PM
To: Tomcat Users List
Cc: Nando Schmitt
Subject: RE: Tomcat5.0.28 character encodingg problem
thanks chris,
our client doesn't want to upgrade to tomecat 5.5 - that's our problem.
Aleksey
From
I am getting the following error in the display of the JSP. To give a
little history, this application I am supporting, at the time the
developers thought they needed to encode the characters to UTF-8 into
our Oracle DB. The developers were unaware they could have allowed the
DB Driver convert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe,
Joe Russo wrote:
I am in the process of converting from using JRUN to Tomcat
Good for you! Welcome to the community.
I have
ran into the problem where these funky symbols are displaying. I can
not find any stack traces that would explain
http://tomcat.apache.org/faq/misc.html#utf8
And you should first start with in server.xml:
Connector ... URIEncoding=UTF-8 .../
-Tim
Joe Russo wrote:
I am getting the following error in the display of the JSP. To give a
little history, this application I am supporting, at the time the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
Nathan Hook wrote:
- Set the meta type in each and every jsp to be utf-8. Now, most
browsers will ignore this value from my understanding, but it shouldn't
hurt to add it.
Really? The HTTP header should override any META tag, but the
I think my statement of most browsers will ignore this value might have
been a tad bit on the excessive side upon further reading and i was hoping
to have that read as don't only rely on using the meta tag.
From my understanding there are broswers where they can set their own
content type no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aleksey,
Aleksey Dayen wrote:
Right now we using TomCat 4.1 with JDK 1.1.
Wow, really? I would think that JDK 1.2 would be the bare minimum for
Tomcat 4.1.
Would our TomCat version work if we update to J2SDK 5.0 with Update 6?
Maybe. IIRC,
: Re: Tomcat5.0.28 character encodingg problem
I think my statement of most browsers will ignore this value might have
been a tad bit on the excessive side upon further reading and i was hoping
to have that read as don't only rely on using the meta tag.
From my understanding there are broswers where
thanks chris,
our client doesn't want to upgrade to tomecat 5.5 - that's our problem.
Aleksey
From: Christopher Schultz [EMAIL PROTECTED]
Sent: Wednesday, July 25, 2007 5:55 PM
To: Tomcat Users List
Subject: Re: Tomcat5.0.28 character encodingg problem
: Re: Tomcat5.0.28 character encodingg problem
Both Chris and Tim are giving great advice. We're actually just trying
to
internationalize our application for our next major release.
Here are the things we've learned.
- You have to change the URIEncoding on your Tomcat Connector in your
Subject: Re: Tomcat5.0.28 character encodingg problem
Date: Wed, 25 Jul 2007 12:09:07 -0400
http://tomcat.apache.org/faq/misc.html#utf8
And you should first start with in server.xml:
Connector ... URIEncoding=UTF-8 .../
-Tim
Joe Russo wrote:
I am getting the following error in the display
11 matches
Mail list logo
