bgsrinivas
asked on
japanese characters in the uri when deployed to tomcat do not work
hi,
I have deployed my application to tomcat 5. 0.25 on a windows-xp japanese machine .
The context name has combination of english and japanese characters.
1.When i launch the application as follows it gives resourse not found exception(Http 404).
http://localhost:portno/applicationname.
The application name is combination of english and japanese characters.
I overcame the problem of http-404 error by setting the encoding to UTF-8 in web.xml and uri encoding to UTF-8 in the connector tag of server.xml.
Now the request comes to my application but req.getsession fails because the context name in the request is not encoded.Even though i have set the encoding to UTF-8 through the following statement
req.setCharacterEncoding(" UTF-8");
The following is the exception :
javax.servlet.ServletExcep tion: app.HServlet.service(): error while processing CMD=null<br>java.lang.Ille galArgumen tException : /appname??
the question marks in '/appname??' are nothing but the japanese characters which are not encoded properly.
Thanks
Srinivas
I have deployed my application to tomcat 5. 0.25 on a windows-xp japanese machine .
The context name has combination of english and japanese characters.
1.When i launch the application as follows it gives resourse not found exception(Http 404).
http://localhost:portno/applicationname.
The application name is combination of english and japanese characters.
I overcame the problem of http-404 error by setting the encoding to UTF-8 in web.xml and uri encoding to UTF-8 in the connector tag of server.xml.
Now the request comes to my application but req.getsession fails because the context name in the request is not encoded.Even though i have set the encoding to UTF-8 through the following statement
req.setCharacterEncoding("
The following is the exception :
javax.servlet.ServletExcep
the question marks in '/appname??' are nothing but the japanese characters which are not encoded properly.
Thanks
Srinivas
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.