Results 1 to 3 of 3

Thread: FlatFileItemProvider - Is it really so?

  1. Nov 16th, 2007, 02:17 PM #1
    sotretus
    sotretus is offline Member
    Join Date
    Sep 2004
    Posts
    54

    Talking FlatFileItemProvider - Is it really so?

    The FlatFileItemProvider is one of the classes I use the most, but there is a tiny little thing that bothers me (I'm being picky here ). It is actually not restricted to Flat Files, or even to Files. As it uses an InputSource to fetch data (actually a FieldSetInputSource) it is totally independent from the source type.

    I would suggest something more like 'FieldSetMapperItemProvider' or that relates more to what it actually does.
    Reply With Quote Reply With Quote
  2. Nov 20th, 2007, 02:11 AM #2
    Dave Syer
    Dave Syer is offline Senior Member
    Join Date
    Jun 2005
    Posts
    4,241

    Default

    That was actually its name in an earlier draft, but we switched to "FlatFile*" on the grounds that this is by far the most common usage, and if people are looking for something to process flat files, then the name will be easy to find.

    If anyone wants to vote for the FieldSet* naming add your comments here...
    Last edited by Dave Syer; Nov 20th, 2007 at 02:13 AM. Reason: spelling
    Reply With Quote Reply With Quote
  3. Nov 26th, 2007, 11:33 AM #3
    lucasward
    lucasward is offline Senior Member
    Join Date
    Dec 2006
    Posts
    1,061

    Default

    I believe the FlatFileItemProvider was removed quite awhile ago in the latest snapshot, although it still exists in milestone 2. The change was part of a fix to move FieldSetMapping into the input source so that more informative exceptions could be thrown when file parsing errors are encountered.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules