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.


2 Responses to “Problems with Jersey, REST, JSON and UTF-8 [Update2]”  

  1. Gravatar Icon 1 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.

  2. Gravatar Icon 2 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.

Leave a Reply



RSS