Code Monkeyism

Programming is hard by Stephan Schmidt

March 24, 2008

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

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.

If you liked this post, subscribe to my free full RSS feed.
Filed under: Java

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.

Get free updates by email

If you did like this article you can get free updates with your RSS reader, you can follow me on Twitter or get free update to new posts by email. Enter your email:

 
About the author: Stephan has been working as a head of development and CTO. He has experiences in different technologies since 20 years including Java, Rails and Python. Stephans main field of interest is maintainablity and productivity in software development. Want to know more? All views are only his own.

Comments

James Lorenzen

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.

March 29th, 2008
stephan

Thanks, that would be great. I’ve got a reply from Paul, see the comments on the other, and I hope the issue is resolved with Jersey 0.7.

March 29th, 2008

Leave a Reply