[ http://jira.codehaus.org/browse/XFIRE-385?page=comments#action_64907 ]
Dan Diephouse commented on XFIRE-385:
-------------------------------------
turns out this content type is valid. But here is the exception Resin is
throwing:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
@40000000445bc2063aa5ec74 [16:22:04.983]
java.nio.charset.IllegalCharsetNameException: UTF-8"
@40000000445bc2063aa5f82c [16:22:04.983] at
java.nio.charset.Charset.checkName(Charset.java:285)
@40000000445bc2063aa5fffc [16:22:04.983] at
java.nio.charset.Charset.lookup2(Charset.java:459)
@40000000445bc2063aa607cc [16:22:04.983] at
java.nio.charset.Charset.lookup(Charset.java:438)
@40000000445bc2063aa60bb4 [16:22:04.983] at
java.nio.charset.Charset.isSupported(Charset.java:477)
@40000000445bc2063aa61384 [16:22:04.983] at
com.caucho.vfs.i18n.JDKWriter$OutputStreamEncodingWriter.<init>(JDKWriter.java:110)
@40000000445bc2063aa66974 [16:22:04.983] at
com.caucho.vfs.i18n.JDKWriter.create(JDKWriter.java:81)
@40000000445bc2063aa67144 [16:22:04.983] at
com.caucho.vfs.i18n.EncodingWriter.create(EncodingWriter.java:82)
@40000000445bc2063aa67914 [16:22:04.983] at
com.caucho.vfs.Encoding.getWriteEncoding(Encoding.java:172)
@40000000445bc2063aa680e4 [16:22:04.983] at
com.caucho.server.connection.ToByteResponseStream.setEncoding(ToByteResponseStream.java:130)
@40000000445bc2063aa6a024 [16:22:04.983] at
com.caucho.server.connection.AbstractHttpResponse.setCharacterEncoding(AbstractHttpResponse.java:1044)
@40000000445bc2063aa6a7f4 [16:22:04.983] at
com.caucho.server.connection.AbstractHttpResponse.setContentType(AbstractHttpResponse.java:1012)
@40000000445bc2063aa6e28c [16:22:04.983] at
org.codehaus.xfire.transport.http.HttpChannel.sendViaServlet(HttpChannel.java:90)
@40000000445bc2063aa6ee44 [16:22:04.983] at
org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:62)
@40000000445bc2063aa6f614 [16:22:04.983] at
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
@40000000445bc2063aa6f9fc [16:22:04.983] at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:98)
> MTOM can respond with an invalid content type
> ---------------------------------------------
>
> Key: XFIRE-385
> URL: http://jira.codehaus.org/browse/XFIRE-385
> Project: XFire
> Type: Bug
> Versions: 1.1-RC1
> Reporter: Dan Diephouse
> Assignee: Dan Diephouse
> Fix For: 1.1
>
>
> For example:
> Content-Type: application/xop+xml; charset=UTF-8; type="text/xml;
> charset=UTF-8"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
