Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 24971 invoked from network); 2 Mar 2011 04:01:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Mar 2011 04:01:17 -0000 Received: (qmail 73803 invoked by uid 500); 2 Mar 2011 04:01:17 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 73379 invoked by uid 500); 2 Mar 2011 04:01:14 -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 73370 invoked by uid 99); 2 Mar 2011 04:01:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 04:01:13 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com designates 209.85.161.173 as permitted sender) Received: from [209.85.161.173] (HELO mail-gx0-f173.google.com) (209.85.161.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 04:01:07 +0000 Received: by gxk28 with SMTP id 28so2676432gxk.32 for ; Tue, 01 Mar 2011 20:00:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IQKXOOI/a9MLgTXQem3Jitzt2GZaq8uMl2F6d1MMvkI=; b=ZN43khVUInbAJG4mqgFdML00R35W67g55HuGj0c6AStgEUJym8xBGgvA99yNKktwhu UULMyWhB2VwOGiMU/7uKqFCOnDHFA0RJoNCpQKB8ts5Yyr/w16cbPiqgwiPj/1TOVqn4 1eb760DKmvlHMqE6cUBhmP8ohAZrSbyQ/0yi0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=LVsY4zEzjxSfmxyN72wvFR4IJnlCs2B1NC3cxq2NvscBbnIdMdULpEibz+wrczB/qd x5kCFlQBE8jtkJPCADdcz0zcek5sYwibwek3FHRRKIz2gLY7uNNdBv0HYGeJkRl0I8Q7 AXHtlz41G4fgSYjK6lw0MjWi3TDRtRMDu1iWE= Received: by 10.151.146.15 with SMTP id y15mr9821866ybn.369.1299038446084; Tue, 01 Mar 2011 20:00:46 -0800 (PST) Received: from [192.168.0.158] ([123.116.38.85]) by mx.google.com with ESMTPS id k1sm3553560ybj.0.2011.03.01.20.00.43 (version=SSLv3 cipher=OTHER); Tue, 01 Mar 2011 20:00:44 -0800 (PST) Message-ID: <4D6DC0E9.2040403@gmail.com> Date: Wed, 02 Mar 2011 12:00:41 +0800 From: Willem Jiang User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: users@camel.apache.org Subject: Re: why camel-jdbc do not return an ArrayList References: <1299037428275-3406057.post@n5.nabble.com> In-Reply-To: <1299037428275-3406057.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Bill, Which version of Camel are you using? I just checked the camel-jdbc code, the result should be List>. You need to use exchange.getOut().getBody().getClass() to print the class of message body. On 3/2/11 11:43 AM, Bill wrote: > Hi, the docs says that the jdbc component returns an ArrayList when post a > query command. > but I only got a JMSMessage. > > -----------------------------when my parms from JMS queue---------- > > > //return the query > command > > > ---------------------------------------------------------------------- > I print the exchange.getOut().getClass() , the infomation is : class > org.apache.camel.component.jms.JmsMessage > and the JmsMessage contains the return rows info:Exchange[JmsMessage: > [{FID=abc1 1956028776, FNUMBER=fff, FCOUNT=1956028776}, {FID=abc1 > 1956028776, FNUMBER=fff, FCOUNT=1956028776}]] > > Why it's not an ArrayList> object? > -- Willem ---------------------------------- FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang