[
https://issues.apache.org/jira/browse/CAMEL-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984349#action_12984349
]
Ashwin Karpe edited comment on CAMEL-3562 at 1/20/11 2:33 PM:
--------------------------------------------------------------
Hi Claus,
I was a little conflicted about it. I wanted to use something that would
indicate that trimming was only applicable to the Unmarshal phase.
I will also change the default as you suggest. I guess given that it is a
different camel version, so long as the documentation is good it should
suffice. I will make both the changes you suggest.
Cheers,
Ashwin...
was (Author: akarpe):
Hi Claus,
I was a little conflicted about it. I wanted to use something that would
indicate that trimming was only applicable to the Unmarshal phase.
I will make the change you suggest.
Cheers,
Ashwin...
> BindyFixedLengthDataFormat does a trim on Fixed Length record
> -------------------------------------------------------------
>
> Key: CAMEL-3562
> URL: https://issues.apache.org/jira/browse/CAMEL-3562
> Project: Camel
> Issue Type: Improvement
> Components: camel-bindy
> Affects Versions: 2.4.0
> Reporter: Ashwin Karpe
> Assignee: Ashwin Karpe
> Attachments: CAMEL-3562.patch
>
>
> BindyFixedLengthDataFormat does a trim on Fixed Length record, although Fixed
> Length recordare strictly positional in nature and may contain lot of fillers
> with empty spaces, doing a trim causes Bindy to fail the message length
> validation and exception is thrown on message length
> // Read the line
> String line = scanner.nextLine().trim();
> Should be changed to
> // Read the line
> String line = scanner.nextLine();
> Or a conditional option should be provided in FixedLengthRecord annotation
> whether or not to trim the entire record
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
