Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <22481379.post@talk.nabble.com>
Date: Thu, 12 Mar 2009 10:24:30 -0700 (PDT)
From: nojonojo <n0_j0@yahoo.com>
To: users@camel.apache.org
Subject: Restlet component and alternate character sets
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


It appears to me that the Restlet component doesn't support character sets
other than the default.  In general, Camel uses the Exchange.CHARSET_NAME
property in the Exchange to determine which character set to use in
conversions between binary and String representations.  The
DefaultRestletBinding doesn't pass this information on to the Restlet
library in the populateRestletResponseFromExchange method.

A simple change makes this work.  Applying the following diff passes the
charset information onto the Restlet component properly:

217a218,221
>         if (exchange.getProperty(Exchange.CHARSET_NAME) != null)
>         {
>        	   
> response.getEntity().setCharacterSet(CharacterSet.valueOf(exchange.getProperty(Exchange.CHARSET_NAME,
> String.class)));
>         }

This sets the characterset for the Restlet representation at the very end of
the populateRestletResponseFromExchange method.

Thanks.

Nolan
-- 
View this message in context: http://www.nabble.com/Restlet-component-and-alternate-character-sets-tp22481379p22481379.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.