camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fried Hoeben (JIRA)" <>
Subject [jira] [Created] (CAMEL-6188) CXF cosumer should set Exchange's charset name, if content type provides one
Date Wed, 20 Mar 2013 13:21:19 GMT
Fried Hoeben created CAMEL-6188:

             Summary: CXF cosumer should set Exchange's charset name, if content type provides
                 Key: CAMEL-6188
             Project: Camel
          Issue Type: Bug
          Components: camel-cxf
    Affects Versions: 2.10.4
            Reporter: Fried Hoeben

The CXF consumer copies the content-type http header to the camel exchange. This header may
indicate the character set used in the request (for instance "text/xml;charset=UTF-8"), and
if so this should be made available in the normal place for Camel (i.e. a property in the
exchange called 'CamelCharsetName').

This may (of course) be done in each route by a separate processor, but it simplifies life
if this is done by default. (org.apache.camel.component.cxf.DefaultCxfBinding.populateExchangeFromCxfRequest()
seems the logical place)

Sample processor that performs this job.
import java.nio.charset.Charset;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;
import org.apache.camel.util.ExchangeHelper;
import org.apache.http.entity.ContentType;

 * Processor to ensure the exchange's charset name property is in sync with
 * its content type.
public class CharsetProcessor implements Processor {
    public void process(Exchange exchange) throws Exception {
        String contentTypeHeader = ExchangeHelper.getContentType(exchange);
        if (contentTypeHeader != null) {
            ContentType contentType = ContentType.parse(contentTypeHeader);
            if (contentType != null) {
                Charset charset = contentType.getCharset();

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message