Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 5446 invoked from network); 31 Aug 2009 15:53:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Aug 2009 15:53:24 -0000 Received: (qmail 9151 invoked by uid 500); 31 Aug 2009 15:53:24 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 9123 invoked by uid 500); 31 Aug 2009 15:53:24 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 9113 invoked by uid 99); 31 Aug 2009 15:53:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 15:53:23 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 31 Aug 2009 15:53:13 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Mi9Bd-0002UZ-7Z for dev@activemq.apache.org; Mon, 31 Aug 2009 08:52:53 -0700 Message-ID: <25225751.post@talk.nabble.com> Date: Mon, 31 Aug 2009 08:52:53 -0700 (PDT) From: rainy3 To: dev@activemq.apache.org Subject: RE: ActiveMQcpp cms::Session::createTextMessage() function usage question with ISO-8859-1 strings In-Reply-To: <1248994012.2590.66.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: rainy3@poczta.onet.pl References: <1248989402.2590.37.camel@localhost> <1248990806.2590.43.camel@localhost> <1248991815.2590.45.camel@localhost> <1248994012.2590.66.camel@localhost> X-Virus-Checked: Checked by ClamAV on apache.org Hello, I just need more clarification on this case. Assume that i have a ActiveMQ broker, java producer and c++ consumer for text messages. Producer read some text from database for example in ISO-8859-1 charset. Then it creates text message (conversion to UTF-8) and send it to broker. Then, finally, consumer won't be able to read this text messages because backward conversion (C++ client) allows only ASCII chars, right? -- View this message in context: http://www.nabble.com/ActiveMQcpp-cms%3A%3ASession%3A%3AcreateTextMessage%28%29-function-usage-question-with-ISO-8859-1-strings-tp24747592p25225751.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.