Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: "Walzer, Thomas" <thomas.walzer@integratix.net>
To: "users@camel.apache.org" <users@camel.apache.org>
Date: Thu, 24 Jan 2013 10:41:46 +0100
Subject: Bindy/FixedLength/encoding/optional fields 
Thread-Topic: Bindy/FixedLength/encoding/optional fields 
Thread-Index: Ac36FwaLu/gGEeyDQkWXtULldD8PgQ==
Message-ID: <5DD232F9-0E80-47F8-BA5E-3E4727498986@integratix.net>
Accept-Language: de-DE
Content-Language: en-US
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi all,

I see strange behaviour in camel-bindy:

1) When I unmarshal a fixed-length file I get errors when the file is encod=
ed in e.g. UTF-8. It seems that characters that need multiple bytes to enco=
de confuse the parser/scanner. There was a JIRA with regard to bindy-csv bu=
t nothing bindy-fixed.

2) The length parameter in the fixedlength-annotation is required (otherwis=
e it is 0). Wouldn=B4t it be nice if this were computed. It would be great =
to have optional fixed-length fields (like in old host files). Or do I have=
 to go the smooks-route?=20

Regards, Thomas.