This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes Internationalization problem in req.getParameter () Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Internationalization problem in req.getParameter ()" Watch "Internationalization problem in req.getParameter ()" New topic

Internationalization problem in req.getParameter ()

Siddharth bal sharma

Joined: Apr 27, 2006
Posts: 8
In Weblogic, req.getParameter() gives encoded data which we need to decode to get value【Number坑坼】string

But in websphere, req.getParameter() directly gives 【Number坑坼】[Looks like WebSphere handles decoding part before returning data]. So the code for decoding logic fails as it tries to decode the data which is already decoded.

In websphere,-Ddefault.client.encoding=UTF-8 argument is specified as a generic JVM argument.If we remove this argument the application is running fine.

Is anyone aware of this behavior?
I agree. Here's the link:
subject: Internationalization problem in req.getParameter ()
It's not a secret anymore!