[
https://issues.apache.org/jira/browse/WINK-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841833#action_12841833
]
Bryant Luk commented on WINK-262:
---------------------------------
Would putting Response.ok(e).contentType("application/xml;charset=(your char
set)").build() work?
As far as Wink automatically determining the charset, I don't know if that's
possible. We would have to read the entire output and "guess" the character
set before we started sending anything in the response (because the charset
must be sent as part of the HTTP headers, if we started sending content with a
large entity, it may be too late to add/change the HTTP header since the entity
data could force a flush of the response to the client). I'm also not too sure
how we could determine the charset correctly (i.e. what if there were
conflicts).
Do you have a suggestion on how to determine that?
> Content-Type of HTTP Response contains no charset.
> --------------------------------------------------
>
> Key: WINK-262
> URL: https://issues.apache.org/jira/browse/WINK-262
> Project: Wink
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.0
> Environment: Jetty Server 6.1
> Reporter: Kaloyan Kolev
>
> I have the following handler:
> {code}
> import javax.ws.rs.GET;
> import javax.ws.rs.Path;
> import javax.ws.rs.Produces;
> import javax.ws.rs.core.Context;
> import javax.ws.rs.core.MediaType;
> import javax.ws.rs.core.Request;
> import javax.ws.rs.core.Response;
> import org.apache.wink.common.model.atom.AtomEntry;
> import org.apache.wink.common.model.atom.AtomText;
> @Path("contentType")
> public class ContentTypeTest {
> @GET
> @Produces( { MediaType.APPLICATION_XML, MediaType.TEXT_XML,
> MediaType.APPLICATION_JSON, "text/javascript" })
> public Response getRepresentation(@Context Request req) {
> AtomEntry e = new AtomEntry();
> e.setTitle(new AtomText(
>
> "\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u4e00\u69cb\u30bd\u30c1\u2010"));
> return Response.ok(e).build();
> }
> }
> {code}
> When I open the resource I get the following HTTP response:
> {code}
> Content-Type: application/xml
> Content-Length: 274
> Server: Jetty(6.1.x)
> {code}
> You can see that the charset is not specified and the content is not properly
> decoded e.g. by RestClient - http://code.google.com/p/rest-client/
> However I can see that the XML is properly encoded by opening the resource in
> FF and enforcing UTF-8 decoding.
> Shouldn't wink put the encoding used during serialization if different than
> ASCII?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
