Comments on: Problems with Jersey, REST, JSON and UTF-8 [Update] http://www.codemonkeyism.com/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/ Programming is hard Sat, 22 Nov 2008 09:51:02 +0000 http://wordpress.org/?v=2.6.3 By: Generic plavix. http://www.codemonkeyism.com/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-161554 Generic plavix. Thu, 04 Sep 2008 17:23:17 +0000 http://stephan.reposita.org/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-161554 <strong>New medication like plavix....</strong> Plavix verses generic. Plavix.... New medication like plavix….

Plavix verses generic. Plavix….

]]> By: Paul Sandoz http://www.codemonkeyism.com/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-66340 Paul Sandoz Tue, 25 Mar 2008 10:47:51 +0000 http://stephan.reposita.org/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-66340 Hi Stephan, Yes, i think this is a problem with Jersey, thanks for reporting it. The EG recently found this issue as well and we have updated the JSR-311 specification, version 0.7 [1], to state: When writing responses, implementations SHOULD respect application-supplied character set metadata and SHOULD use UTF-8 if a character set is not specified by the application or if the application specifies a character set that is unsupported. and this will be implemented in the 0.7 release of Jersey (scheduled for April 18th). I should be able to provide you with a specific solution for StringProvider fairly quickly if you are happy working with the latest builds or the trunk. Paul. [1] https://jsr311.dev.java.net/ Hi Stephan,

Yes, i think this is a problem with Jersey, thanks for reporting it.

The EG recently found this issue as well and we have updated the JSR-311 specification, version 0.7 [1], to state:

When writing responses, implementations SHOULD respect application-supplied character set
metadata and SHOULD use UTF-8 if a character set is not specified by the application or if the
application specifies a character set that is unsupported.

and this will be implemented in the 0.7 release of Jersey (scheduled for April 18th).

I should be able to provide you with a specific solution for StringProvider fairly quickly if you are happy working with the latest builds or the trunk.

Paul.

[1] https://jsr311.dev.java.net/

]]> By: Problems with Jersey, REST, JSON and UTF-8 [Update2] at Stephans Blog http://www.codemonkeyism.com/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-66063 Problems with Jersey, REST, JSON and UTF-8 [Update2] at Stephans Blog Mon, 24 Mar 2008 11:24:55 +0000 http://stephan.reposita.org/archives/2008/03/22/problems-with-jersey-rest-json-and-utf-8/#comment-66063 [...] No signal, no noise. « Problems with Jersey, REST, JSON and UTF-8 [Update] [...] [...] No signal, no noise. « Problems with Jersey, REST, JSON and UTF-8 [Update] [...]

]]>