Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 62033 invoked from network); 26 Oct 2006 05:53:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 05:53:07 -0000 Received: (qmail 77466 invoked by uid 500); 25 Oct 2006 01:26:38 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 77455 invoked by uid 500); 25 Oct 2006 01:26:38 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 77445 invoked by uid 99); 25 Oct 2006 01:26:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2006 18:26:38 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of chirino@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2006 18:26:26 -0700 Received: by ug-out-1314.google.com with SMTP id 29so1813352ugc for ; Tue, 24 Oct 2006 18:26:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=j6i072Gzb1fKZXgLsDDyV1KlI248CYlU2q+VMbR23m7tdjk0TR4wwXlyU3S0BzavZAk1e/A51KesUOqzskqveP0wWrVOMPTe4YRH53K4Jfpn2yl2telPTJyOrHl5yIIZsfuVB6Am3XzXgnpkLC++CMVeAAq80JxjTXWkiuQAVgw= Received: by 10.78.150.7 with SMTP id x7mr89745hud; Tue, 24 Oct 2006 18:26:05 -0700 (PDT) Received: by 10.78.148.15 with HTTP; Tue, 24 Oct 2006 18:26:04 -0700 (PDT) Message-ID: Date: Tue, 24 Oct 2006 21:26:04 -0400 From: "Hiram Chirino" Sender: chirino@gmail.com To: activemq-users@geronimo.apache.org Subject: Re: Ruby STOMP client - TextMessage In-Reply-To: <6983941.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14529_12297850.1161739564915" References: <6983941.post@talk.nabble.com> X-Google-Sender-Auth: d17c99f90bf75798 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_14529_12297850.1161739564915 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Sounds valid. Send us the patch. On 10/24/06, robottaway wrote: > > > I am using the Ruby STOMP client. I would like the STOMP transport in AMQ > to > convert incoming STOMP messages to TextMessage rather than ByteMessage. > How > can I do this? I see lots of info on not setting a content-length header. > The Ruby STOMP client sets this header to the size of the message body > though, so the content-length header is always set :( > > Okay I was writing the above when I decided to just try hacking the > stomp.rb > file. I commented out the section where _transmit sets the content-length > header to the text's size. This worked like a charm! Is this okay to do > though? > -- > View this message in context: > http://www.nabble.com/Ruby-STOMP-client---TextMessage-tf2504913.html#a6983941 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com ------=_Part_14529_12297850.1161739564915--