Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E4BC8200CF7 for ; Tue, 19 Sep 2017 20:07:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E359B1609DD; Tue, 19 Sep 2017 18:07:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 347981609BF for ; Tue, 19 Sep 2017 20:07:03 +0200 (CEST) Received: (qmail 48626 invoked by uid 500); 19 Sep 2017 18:07:02 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 48615 invoked by uid 99); 19 Sep 2017 18:07:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Sep 2017 18:07:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F00DECFA43 for ; Tue, 19 Sep 2017 18:07:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FFEN-v5PxesP for ; Tue, 19 Sep 2017 18:07:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2EB645F4E5 for ; Tue, 19 Sep 2017 18:07:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8F8B0E0E3F for ; Tue, 19 Sep 2017 18:07:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1CEB2244F9 for ; Tue, 19 Sep 2017 18:07:00 +0000 (UTC) Date: Tue, 19 Sep 2017 18:07:00 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CAMEL-11479) beanio - Unmarshalling multiline values as multiple records MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 19 Sep 2017 18:07:04 -0000 [ https://issues.apache.org/jira/browse/CAMEL-11479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172103#comment-16172103 ] Claus Ibsen commented on CAMEL-11479: ------------------------------------- Okay this is not supported as camel-beanio uses beanio's Reader (when you use dataformat unmarshal) and this Reader is for reading multiple records. Its unusual to just read a single record and therefore was not supported. Typically people have a row of records they want to unmarshal to a List classes, and hence why the reader is in-use. > beanio - Unmarshalling multiline values as multiple records > ----------------------------------------------------------- > > Key: CAMEL-11479 > URL: https://issues.apache.org/jira/browse/CAMEL-11479 > Project: Camel > Issue Type: Improvement > Components: camel-beanio > Reporter: Manikanta A C > Priority: Minor > > Referring to the example in http://camel.apache.org/beanio.html, we have a simple mapping file & a message with value spans more than one line. > Using camel-beanio, only the contents in first line in the message is being read a one record into the exchange's body at one iteration. > The next line is being treated as new record and unmarshalling breaks as BeanIOErrorHandler warns it as invalid record. > We had to add a camel processor to remove the line breaks in the message before unmarshalling to read complete multi-line message, which may not be the best solution in all real time cases. > Does camel-beanio read each line as different record? > Is there any other way to still read multi-line values as single record using camel-beanio? -- This message was sent by Atlassian JIRA (v6.4.14#64029)