Written on March 24, 2008 by Stephan Schmidt

Problems with Jersey, REST, JSON and UTF-8 [Update2]

2 Comments Comments Icon

I’ve written about my UTF-8 woes with Jersey. Digging through the code of Jersey hasn’t resulted in any clues yet. I’m still not sure how to set an UTF-8 content header for HTTP with Jersey. Other impression from the code: no JavaDoc. Usually not a good sign. I’ll keep you updated on my progress through Jersey code depths.

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

About the author: Stephan Schmidt is head of development at brands4friends. He has more than 15 years of internet technology experience and 10 years experience in agile. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own.

Comments

James Lorenzen

March 29th, 2008

Funny. my team is currently doing a lot with utf-8, with jersey, and extjs for javascript i8ln support.
I believe we got around some of the issues by setting the response content type to text/html.
I am going to forward them this blog and they should comment on their solutions.

stephan