2007/11/19, Ognjen Blagojevic <[EMAIL PROTECTED]>:
> I suppose you are using ActionForms. Try to extend ActionForm overriding
> your reset method which will set the character encoding, before the
> parameters are processed. Something like this:
well, I solved with a Valve that impose a default enc
Tremal Naik wrote:
Oh, yes, you're right. I'm using version 1.1, that's why probably I
don't have that option available. Unfortunately I'm not allowed to
upgrade to a newer version...
I suppose you are using ActionForms. Try to extend ActionForm overriding
your reset method which will set the
2007/11/19, Ognjen Blagojevic <[EMAIL PROTECTED]>:
> Which version of Struts are you using? 1.2.7 does support acceptCharset,
> as you can see here:
Oh, yes, you're right. I'm using version 1.1, that's why probably I
don't have that option available. Unfortunately I'm not allowed to
upgrade to a
Tremal Naik wrote:
2007/11/16, Ognjen Blagojevic <[EMAIL PROTECTED]>:
Did you try to put acceptCharset="UTF-8" in the form tag?
well, I'm using Struts and it looks the html:form tag doesn't allow
any acceptCharset attribute. I tried to set the enctype attribute, but
with no effect.
Which ver
2007/11/16, Mark Thomas <[EMAIL PROTECTED]>:
>
> Some standard text I wrote a while ago follows. The most useful bit is
> probably the URIEncoding attribute on the connector.
Thanks Mark, I think I read your paper somewhere before I decided to
write to this help request. In fact, if you read caref
Michael wrote:
>
> start your JVM with -Dfile.encoding=UTF-8 and try again!
That property is read-only on some JVMs and is not the way to achieve what
the OP is trying to do.
Some standard text I wrote a while ago follows. The most useful bit is
probably the URIEncoding attribute on the connecto
2007/11/16, Ognjen Blagojevic <[EMAIL PROTECTED]>:
> Did you try to put acceptCharset="UTF-8" in the form tag?
well, I'm using Struts and it looks the html:form tag doesn't allow
any acceptCharset attribute. I tried to set the enctype attribute, but
with no effect.
Thanks,
--
TREMALNAIK
--
start your JVM with -Dfile.encoding=UTF-8 and try again!
bye
--
OOXML - Say NO To Microsoft Office broken standard
http://www.noooxml.org
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL P
2007/11/16, Mohsen Saboorian <[EMAIL PROTECTED]>:
> I don't know if this is the best solution. You can create a filter for
> *.* in your web.xml, with the following piece of code:
> response.setCharacterEncoding("UTF-8");
No, unfortunately the parameters are parsed before any filter is
invoked. He
Hi Tremal,
Tremal Naik wrote:
all characters are displayed well in both browsers, the page encoding
appears correctly set to UTF-8. The problems arises when I try to
submit "strange" characters as currency symbols (euro, pound, yen,
...) in a form text box.
Did you try to put acceptCharset="UT
2007/11/16, Tremal Naik <[EMAIL PROTECTED]>:
> No, unfortunately the parameters are parsed before any filter is
> invoked. Hence, a flag is set on the request that avoids subsequent
I tried with valve. It looks fine now.
But it's really annoying having to impose a default character encoding
usin
Hi,
I don't know if this is the best solution. You can create a filter for
*.* in your web.xml, with the following piece of code:
response.setCharacterEncoding("UTF-8");
Mohsen.
On Nov 16, 2007 4:44 PM, Tremal Naik <[EMAIL PROTECTED]> wrote:
> Hello Tomcat users,
> I'm developing an application
Hello Tomcat users,
I'm developing an application in Jboss 4.0.2, which uses Tomcat 5.5.9
as web tier.
I'm trying to make Tomcat decoding the request body with the correct
encoding. I have problems with IE and Firefox as well. The html page
has the meta tag:
all characters are display
13 matches
Mail list logo
