Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 66273 invoked from network); 7 Apr 2010 09:50:09 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Apr 2010 09:50:09 -0000 Received: (qmail 26727 invoked by uid 500); 7 Apr 2010 09:50:09 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 26700 invoked by uid 500); 7 Apr 2010 09:50:09 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 26692 invoked by uid 99); 7 Apr 2010 09:50:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Apr 2010 09:50:08 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of norman.maurer@googlemail.com designates 209.85.218.215 as permitted sender) Received: from [209.85.218.215] (HELO mail-bw0-f215.google.com) (209.85.218.215) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Apr 2010 09:50:03 +0000 Received: by bwz7 with SMTP id 7so696770bwz.36 for ; Wed, 07 Apr 2010 02:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=YoiFAYzV3mC8YiLYLeNiPre9vTdhntgfdxpTObNsl0A=; b=XiMVaafsC4a5sy+rJwv4GfaU9vP0e0ciSOxG2xfbFIvYwdP+zkLw08I06k64ieABGx TvvK2zYkMU4ga61kwulPB2+HQgAR5kEw8fdvfxrio490riOMcRx/OnJaKd0dE6s1LI+G RmY0hY6if/Ym4bRCfFXZFAbak403K4c7BSZLo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=fZJGqWRgpu6wI+pmedx62YaaTzwVDX9w40VcubyKAbmhssVQwLK9Q5mjYwAqh9Hrku /GgAaAXOzuzwAgG/QKMNBXQjJKljw2vRFHKXtsUIIzpIlB+qGeF3pwgzj1JMkwMBE08y 39xhLEAbTemQQsl3w7nULeFwJUWcIr8981zbM= MIME-Version: 1.0 Received: by 10.204.70.148 with HTTP; Wed, 7 Apr 2010 02:49:41 -0700 (PDT) In-Reply-To: References: Date: Wed, 7 Apr 2010 11:49:41 +0200 Received: by 10.204.133.146 with SMTP id f18mr8876337bkt.153.1270633782750; Wed, 07 Apr 2010 02:49:42 -0700 (PDT) Message-ID: Subject: Re: ActiveMQ component and StreamMessage / BlobMessage From: Norman Maurer To: users@camel.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Maybe I should stopping getting on your nerves and just contribute a patch = ;) Bye, Norman 2010/4/7 Norman Maurer : > Hi Claus, > > thx for your response :) > > If you look at the documentation of BlobMessage how the message is > send via the producer in activemq: > http://activemq.apache.org/blob-messages.html > > So it would be useful if it would be possible to set the "URL" which > is used by the activemq producer to send the message. The second thing > which would be cool is the possibility to send the body of the camel > message via a BlobMessage. Something like this: > > InputStream in =3D exchange.getIn().getBody(InputStream.class); > BlobMessage message =3D session.createBlobMessage(in); > activemqproducer.send(message); > > > The same goes for the consumer. If the cosumed message of activemq is > of the type BlobMessage it should be possible to "cascade" the > getBody() to get the InputStream of the BlobMessage. So the > TypeConverter would do something like this on > getBody(InputStream.class): > > BlobMessage blobMessage =3D (BlobMessage) message; > InputStream in =3D blobMessage.getInputStream(); > return in; > > Thx, > Norman > > > 2010/4/7 Claus Ibsen : >> Hi >> >> ActiveMQ does not output any javax.jms.StreamMessage, and therfore >> Camel have never needed to map it. >> And I also do not think javax.jms.StreamMessage is used very much? >> Anyone every used them? >> >> In terms of BlobMessage. Can you elaborate a bit? Is there anything in >> the BlobMessage API you needed from Camel? >> Doesn't you get all the data from the blob as a inputstream or the likes= ? >> >> >> >> >> On Fri, Apr 2, 2010 at 7:48 PM, Norman Maurer wrote: >>> Hi all, >>> >>> =A0from the Camel in Action book and online docs I see how objects get >>> mapped to the corresponding JMS Message type. I saw that InputStream >>> get mapped to ByteMessage. I wonder why its not using StreamMessage. >>> Anyone knows why ? I thought use StreamMessages would give a real >>> benifit when using big messages. >>> The other thing I would like to see is be able to use BlobMessage when >>> using ActiveMQ component. Is there any plan to support this ? >>> >>> >>> Thx, >>> Norman >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> >