Glad it works.
Look at the sources : it probably forces request/response encoding by
calling :
http://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#setCharacterEncoding(java.lang.String)
Cheers
Rémi
2015-02-27 13:15 GMT+01:00 Nahid Seidi nahid.se...@gmail.com:
Thank you
Nahid,
Ah, good find by everyone that your server isn't in UTF-8.
If you are using Resin, just put this in your resin configuration file:
character-encodingutf-8/character-encoding
That should fix the issue without the need for a filter.
-- Rick
On Fri, Feb 27, 2015 at 6:15 AM, Nahid Seidi
What are the disadvantages of always having the server configured for UTF-8?
On Fri, Feb 27, 2015 at 4:48 AM, Rick Grashel rgras...@gmail.com wrote:
Nahid,
Ah, good find by everyone that your server isn't in UTF-8.
If you are using Resin, just put this in your resin configuration file:
Rusty, there really aren't any. It depends on your perspective. Personally,
I think some low level things and services are better to be handed by the
application server. Default character encoding is one of those. It all
depends on how you view a container and the services you think it should
and
Nahid,
The servlet filter makes your app portable without any server config
required. I'd keep the filter if I were you.
That's why it's included in almost every framework out there. We could add
this as a core functionality into Stripes dispatching : it's easy, and
quite the recurrent feature.
Ok, thanks. Googling brought up this answer as to why it's not using UTF-8.
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
On Fri, Feb 27, 2015 at 10:49 AM, Rick Grashel rgras...@gmail.com wrote:
Rusty, there really aren't any. It depends on your perspective.
Personally, I think some
Rick,
I already tried the encoding tag, but it doesn't work. As I said, I don't
think the problem is with encoding because as you see in the first jsp I
get 'fname' form an actionbean and then send that to another one. Since
'fname' is shown correctly in first jsp but not in second jsp so I don't
Hello,
If you're using Tomcat:
- Such a filter is provided by Tomcat:
https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/filters/SetCharacterEncodingFilter.html
- Or you can force Tomcat to use UTF-8 at the Connector level: Connector
port=8080 *URIEncoding=UTF-8*/
Hi Gérald
I'm using Resin. I guess I need to find out how to do the configuration you
sent in resin.
/Nahid
On Friday, February 27, 2015, Gérald Quintana gerald.quint...@gmail.com
wrote:
Hello,
If you're using Tomcat:
- Such a filter is provided by Tomcat:
Hi,
I'd say Nestor is right. You app server is probably using platform locale.
You probably want this kind of filter :
https://github.com/pojosontheweb/woko/blob/develop/core/src/main/java/woko/util/SetCharacterEncodingFilter.java
And configure it to use utf-8.
Cheers
Rémi
2015-02-27 9:42
Nahid,
I've never had a problem with encoding the contents of a parameter. Try
again with this at the very top of your JSP or the very top of your stripes
template:
%@ page contentType=text/html; charset=UTF-8 %
Thanks.
-- Rick
On Thu, Feb 26, 2015 at 5:27 PM, Nahid Seidi
Hi, I think this problem is related to encoding. You can try a Servlet
filter mapped to /* and call the methods setCharacterEncoding(UTF-8) of
HttpServletResponse and HttpServletRequest
El feb 26, 2015 6:29 PM, Nahid Seidi nahid.se...@gmail.com escribió:
Hi
I am sending some variables from
12 matches
Mail list logo
