You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Michael Allman (JIRA)" <ji...@apache.org> on 2009/10/15 10:46:31 UTC
[jira] Created: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
When writing XML response, CXF uses request encoding instead of response encoding
---------------------------------------------------------------------------------
Key: CXF-2475
URL: https://issues.apache.org/jira/browse/CXF-2475
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.2.4, 2.2.5
Reporter: Michael Allman
Priority: Minor
When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766105#action_12766105 ]
Sergey Beryozkin commented on CXF-2475:
---------------------------------------
CXF JAXRS does not supportn back channels yet (AFAIK they're for handling things like WS-Addressing ?) but generally, if the service declares :
@Produces("text/xml;charset=blah")
then the response will contain ContentType=text/xml;charset=blah
so basically it is the server which dictates.
I guess there could be some subtleties in SOAP-based processing. I'd propose for a patch be updated such that a Message property like BackChannelCharset is checked (or UseServletResponseCharset), if it's not present then the incoming request's charset is used otherwise the custom one/servlet response's is used instead
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766194#action_12766194 ]
Michael Allman commented on CXF-2475:
-------------------------------------
In light of your explanation, I agree that using setCharacterEncoding is not the right way to go.
I will try the ctx.getMessageContext().put(Message.ENCODING, "UTF-8") approach, but I don't know when I will be able to. I should be able to try it tonight at the latest. If that works, it sounds like the cleanest solution.
Also, I agree it makes more sense that character encoding be set on a per-operation basis.
Thanks.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766037#action_12766037 ]
Benson Margulies commented on CXF-2475:
---------------------------------------
I don't think it's counter-intuitive. I don't know what would set the response encoding, and the classic convention is to reply with the encoding of the request.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778254#action_12778254 ]
Michael Allman commented on CXF-2475:
-------------------------------------
Give me a few more days to get back to you. My client's system is down. Thanks.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Allman updated CXF-2475:
--------------------------------
Attachment: AbstractHTTPDestination.patch
Proposed fix. This seems counterintuitive, but after searching for a more elegant solution, this is the best I came up with. Perhaps a regular committer can do this better?
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766058#action_12766058 ]
Daniel Kulp commented on CXF-2475:
----------------------------------
This is working exactly as it's supposed to and this patch completely breaks things all over the place.
By default, nothing sets the the character encoding on the response. Thus, normally, whenever you call getCharacterEncoding(), it will return "ISO-8859-1" which is the default. This breaks all kinds of things that try to send strings and such outside the ISO-8859-1 character space.
According to the specs and WSI-BP, the current behavior is correct. We should be responding with the character set as what the client sent the incoming message with. If the client sent in UTF-8, we respond with UTF-8. If they send with UTF-16, we respond in kind.
Anyway, what is the use case that makes you think this is a bug that needs fixing?
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766469#action_12766469 ]
Michael Allman commented on CXF-2475:
-------------------------------------
I played with implementing ctx.getMessageContext().put(Message.ENCODING, "UTF-8") and couldn't get it to work.
Then I had the realization that this is not the way to go. This approach assumes the service is a JAX-WS service. What if it isn't?
In my case, I'm not using a JAX-WS service.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766083#action_12766083 ]
Michael Allman commented on CXF-2475:
-------------------------------------
Also, I'm not too surprised this patch breaks things. It doesn't really look right to me. It just works in my use case, and I couldn't find a better way to achieve my end. I'm sorry it's a bad patch.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2475.
------------------------------
Resolution: Invalid
Fix Version/s: Invalid
More or less working as designed.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Fix For: Invalid
>
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766082#action_12766082 ]
Michael Allman commented on CXF-2475:
-------------------------------------
I don't understand how this can be the correct behavior.
First, can you tell me what section in what spec states that the character set of the response should be the same as the character set of the request? I searched WSI-BP and SOAP 1.2 and didn't find it.
Now here's why I think this can't be the correct behavior. Suppose a Web service client sends an ISO-8859-1 encoded SOAP request to a Web service and the response document is encoded in UTF-8. (For example, a client queries a Unicode database.) If cxf sets the servlet response encoding to ISO-8859-1 and the response document includes characters outside ISO-8859-1, the response will be defective.
In my particular case, I have a subclass of CXFNonSpringServlet called DatabaseWebServiceServlet. The first thing the invoke method of this class does is set the response encoding to UTF-8 so that I can successfully write a UTF-8 document. I expect cxf to respect that setting.
Also, on the topic of standards, consider HTTP 1.1. If the client expects the response to be encoded in a certain character set, it should specify it in the "Accept-Charset" request header (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.2). Otherwise, the server is free to choose whatever character encoding it wants for the response document.
Anyway, I don't see why the request document character set should be coupled to the response document character set. The "Content-Type" is an entity header that tells the recipient the media type (including charset where applicable) of the entity body (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17). There's nothing in the HTTP 1.1 spec that says this header, when used in a request, specifies what the response media type or character set should be.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-2475) When writing XML response,
CXF uses request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766082#action_12766082 ]
Michael Allman edited comment on CXF-2475 at 10/15/09 8:07 AM:
---------------------------------------------------------------
I don't understand how this can be the correct behavior.
First, can you tell me what section in what spec states that the character set of the response should be the same as the character set of the request? I searched WSI-BP and SOAP 1.2 and didn't find it.
Now here's why I think this can't be the correct behavior. Suppose a Web service client sends an ISO-8859-1 encoded SOAP request to a Web service and the response document is encoded in UTF-8. (For example, a client queries a Unicode database.) If cxf sets the servlet response encoding to ISO-8859-1 and the response document includes characters outside ISO-8859-1, the response will be defective.
In my particular case, I have a subclass of CXFNonSpringServlet called DatabaseWebServiceServlet. The first thing the invoke method of this class does is set the response encoding to UTF-8 so that I can successfully write a UTF-8 document. I expect cxf to respect that setting.
Also, on the topic of standards, consider HTTP 1.1. If the client expects the response to be encoded in a certain character set, it should specify it in the "Accept-Charset" request header (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.2 ). Otherwise, the server is free to choose whatever character encoding it wants for the response document.
Anyway, I don't see why the request document character set should be coupled to the response document character set. The "Content-Type" is an entity header that tells the recipient the media type (including charset where applicable) of the entity body (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17 ). There's nothing in the HTTP 1.1 spec that says this header, when used in a request, specifies what the response media type or character set should be.
was (Author: msa@allman.ms):
I don't understand how this can be the correct behavior.
First, can you tell me what section in what spec states that the character set of the response should be the same as the character set of the request? I searched WSI-BP and SOAP 1.2 and didn't find it.
Now here's why I think this can't be the correct behavior. Suppose a Web service client sends an ISO-8859-1 encoded SOAP request to a Web service and the response document is encoded in UTF-8. (For example, a client queries a Unicode database.) If cxf sets the servlet response encoding to ISO-8859-1 and the response document includes characters outside ISO-8859-1, the response will be defective.
In my particular case, I have a subclass of CXFNonSpringServlet called DatabaseWebServiceServlet. The first thing the invoke method of this class does is set the response encoding to UTF-8 so that I can successfully write a UTF-8 document. I expect cxf to respect that setting.
Also, on the topic of standards, consider HTTP 1.1. If the client expects the response to be encoded in a certain character set, it should specify it in the "Accept-Charset" request header (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.2). Otherwise, the server is free to choose whatever character encoding it wants for the response document.
Anyway, I don't see why the request document character set should be coupled to the response document character set. The "Content-Type" is an entity header that tells the recipient the media type (including charset where applicable) of the entity body (see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.17). There's nothing in the HTTP 1.1 spec that says this header, when used in a request, specifies what the response media type or character set should be.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766170#action_12766170 ]
Daniel Kulp commented on CXF-2475:
----------------------------------
Let me try and rephrase the issue:
When producing a response, in the absence of a user override (more on this in a second), CXF (or any service) needs to choose some charset in which to generate the response. There are several options that can be chosen:
1) Use the Accept-Charset header - this would be ideal except that nobody uses it. I don't think any of the soap toolkit actually send it. That said, if it's there it would probably be good to use. Not using it is probably considered a bug. If it's not there, we need to fall down to other options.
2) Always use UTF-8 - definitely a viable option now and might make sense to do. The PROBLEM with this that we encountered early in the soap days (think 2000-2003 timeframes and such) is that not all embedded devices and such understood UTF-8. Think about things like the embedded stuff in the LeapFrog Leapster toys and such that aren't running java. You could probably argue that they should then send an Accept-Charset, but they don't.
3) Use the incoming request charset - we went this option because if they sent it in that charset, we know they understand it (in theory, otherwise, how would they be able to send it).
Anyway, in the early days of soap interopability testing, option 3 was pretty much determined to be the best option to make sure clients could understand the responses. That said, all the modern things all talk utf-8 pretty well, thus we could possibly change it to default to utf-8.
Now, the question this issue really raises is "if I don't want the above behavior, how do I override it?" which is definitely a valid question. You are trying to override it by calling setCharacterEncoding(...) on the HttpServletResponse object prior to CXF doing anything with it. To me, that is not really an approriate way for a couple reasons:
1) There isn't a way to determine if you called setCharacterEncoding or not. If getCharacterEncoding would return null if set wasn't called, that would be one thing. However, getCharacterEncoding() returns ISO-8859-1(per servlet spec) if set isn't called. Thus, we have no idea if you had called setCharacterEncoding("ISO-8859-1") and really want that or not.
2) Requires a subclass of the CXF servlet or similar to set it. Not something we normally would encourage. It also doesn't work for the embedded Jetty case. Also doesn't work for the other transports like JMS and the Local transport.
#2 is kind of key. Whatever mechanism is chosen, it needs to work for all the various transports. Also, it needs to be able to be set on a per-invokation basis based on knowledge of what is being generated/returned.
I THINK (haven't actually tried this) that it can easily be achieved today via the WebServiceContext. ctx.getMessageContext().put(Message.ENCODING, "UTF-8"); in the service method probably will do it. An interceptor on the out chain could also do it. We could also provide a contextual property (configurable per-endpoint or bus in the spring config) to specify a default as well if we thought that made sense.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770177#action_12770177 ]
Daniel Kulp commented on CXF-2475:
----------------------------------
For non-jaxws, only slightly different:
PhaseInterceptorChain.getCurrentMessage().put(Message.ENCODING, "UTF-8");
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776638#action_12776638 ]
Daniel Kulp commented on CXF-2475:
----------------------------------
Did the above work?
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2475) When writing XML response, CXF uses
request encoding instead of response encoding
Posted by "Michael Allman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778906#action_12778906 ]
Michael Allman commented on CXF-2475:
-------------------------------------
Yes, this works. Thank you.
> When writing XML response, CXF uses request encoding instead of response encoding
> ---------------------------------------------------------------------------------
>
> Key: CXF-2475
> URL: https://issues.apache.org/jira/browse/CXF-2475
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.2.4, 2.2.5
> Reporter: Michael Allman
> Priority: Minor
> Attachments: AbstractHTTPDestination.patch
>
>
> When writing the SOAP XML response, CXF uses the ServletRequest encoding instead of the ServletResponse encoding.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.