Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1FE6510A91 for ; Fri, 12 Jul 2013 02:18:14 +0000 (UTC) Received: (qmail 93543 invoked by uid 500); 12 Jul 2013 02:18:13 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 93508 invoked by uid 500); 12 Jul 2013 02:18:13 -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 93500 invoked by uid 99); 12 Jul 2013 02:18:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jul 2013 02:18:13 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com designates 209.85.160.49 as permitted sender) Received: from [209.85.160.49] (HELO mail-pb0-f49.google.com) (209.85.160.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jul 2013 02:18:09 +0000 Received: by mail-pb0-f49.google.com with SMTP id jt11so8530843pbb.22 for ; Thu, 11 Jul 2013 19:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type:content-transfer-encoding :content-disposition; bh=mfijd9GCxuu9Jr9U2frmDMiKkIvNaLLVQPReBOjNzBQ=; b=B0+pks1OZP53Z5oQe+OHU1MlWY2QCACVog1HpNYslD1r/aYPcrSehhpesIlDk3FxiX SQGjAvVizsJZnQNnMlqJpcTyBy5rtUtOgEVbiHyFXSUW1KhPFx+wVVyDdQXJXIPfvTBz mO7EEGgjMo0CgfTP/ZeWliS38iLy/6aE8GKoSBlCiJv4V+kG0yyeyyVkf9/UvCNPEYNA DQ+nvW8T8jTyVnrCKX1pesvWFYTBKWJm5UYvU0yBZR0QWOOKzImTMOmJWBbWMMqehial iqh/iDCVf3p6YJLzNo88BJt+SQonxv4uXKdT+HXL6NFSa+ZOi8ZPRDo8KrYPLNPTgEKB pCwg== X-Received: by 10.68.235.9 with SMTP id ui9mr30206412pbc.85.1373595469329; Thu, 11 Jul 2013 19:17:49 -0700 (PDT) Received: from [10.66.16.117] ([203.114.244.88]) by mx.google.com with ESMTPSA id cx3sm42456969pbb.30.2013.07.11.19.17.47 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 11 Jul 2013 19:17:48 -0700 (PDT) Date: Fri, 12 Jul 2013 10:17:42 +0800 From: Willem jiang To: users@camel.apache.org Message-ID: In-Reply-To: <1373569143750-5735541.post@n5.nabble.com> References: <1373569143750-5735541.post@n5.nabble.com> Subject: Re: Using Bindy for multiple record types in the same file X-Mailer: sparrow 1.6.4 (build 1176) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org I think you can split the file and routing the lines to different bindy d= ata format base on the first 2 character. -- =20 Willem Jiang Red Hat, Inc. =46useSource is now part of Red Hat Web: http://www.fusesource.com =7C http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) = (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang =20 Weibo: =E5=A7=9C=E5=AE=81willem On =46riday, July 12, 2013 at 2:59 AM, rodrickmusser wrote: > I am wondering if Bindy can be used in the following scenario: > =20 > The file format I am working with is fixed length. The first two charac= ters > indicate the record type. =46or example, =2201=22 indicates an order re= cord, =2202=22 > indicates a customer record. If the record is an order record, characte= rs > 2-11 are the order id. If the record is a customer record, characters 2= -20 > is the customer name. > =20 > How does Bindy handle this situation=3F > =20 > =20 > =20 > -- > View this message in context: http://camel.465427.n5.nabble.com/Using-B= indy-for-multiple-record-types-in-the-same-file-tp5735541.html > Sent from the Camel - Users mailing list archive at Nabble.com (http://= Nabble.com).