ilyn.org/xsd/smooks-1.1.xsd" xmlns:csv="http://www.milyn.org/xsd/smooks/csv-1.2.xsd"> <csv:reader fields="" separator="" quote="" skipLines="" rootElementName="" recordElementName=""> <csv:singleBinding beanId="" class="" /> </csv:reader> </smooks-resource-list>
To maintain a {@link List} of binding instances in memory:
<?xml version="1.0"?> <smooks-resource-list xmlns="http://www.milyn.org/xsd/smooks-1.1.xsd" xmlns:csv="http://www.milyn.org/xsd/smooks/csv-1.2.xsd"> <csv:reader fields="" separator="" quote="" skipLines="" rootElementName="" recordElementName=""> <csv:listBinding beanId="" class="" /> </csv:reader> </smooks-resource-list>
To maintain a {@link Map} of binding instances in memory:
<?xml version="1.0"?> <smooks-resource-list xmlns="http://www.milyn.org/xsd/smooks-1.1.xsd" xmlns:csv="http://www.milyn.org/xsd/smooks/csv-1.2.xsd"> <csv:reader fields="" separator="" quote="" skipLines="" rootElementName="" recordElementName=""> <csv:mapBinding beanId="" class="" keyField="" /> </csv:reader> </smooks-resource-list>
Strict parsing
Strict parsing was the only option until Smooks 1.2.x, whereby lines that would not comply with the provided tokens (that it where the tokens present in the line is less than the number of tokens expected) would be garbled and a WARN log statement was provided. Now, you can decide if you want those lines to be parsed too, this is accomplished by setting strict="false" on the config.
String manipulation functions
String manipulation functions can be defined per field. These functions are executed before that the data is converted into SAX events. The functions are defined after the field name, separated with a question mark. So a field definition with string functions could look like this: firstname?trim,lastname?right_trim,gender?upper_case Take a look in the Smooks manual for a list of all available functions.
Ignoring Fields
To ignore a field in a CSV record set, just insert the string "
$ignore$" for that field in the fields attribute.
Simple Java Bindings
A simple java binding can be configured on the reader configuration. This allows quick binding configuration where the CSV records map cleanly to the target bean. For more complex bindings, use the Java Binging Framework.
Example Usage
So the following configuration could be used to parse a CSV stream into a stream of SAX events:
<csv:reader fields="name,address,$ignore$,item,quantity" />
Within Smooks, the stream of SAX events generated by the "Acme-Order-List" message (and this parser) will generate an event stream equivalent to the following:
<csv-set> <csv-record number="1"> <name>Tom Fennelly</name> <address>Ireland</address> <item>V1234</item> <quantity>3</quantity> <csv-record> <csv-record number="2"> <name>Joe Bloggs</name> <address>England</address> <item>D9123</item> <quantity>7</quantity> <csv-record> </csv-set>
Other profile based transformations can then be used to transform the CSV records in accordance with the requirements of the consuming entities.
@author tfennelly
@deprecated Use the {@link org.milyn.flatfile.FlatFileReader} configured with the {@link CSVRecordParserFactory}.