Java Reference
In-Depth Information
Listing 10-10.
CustomerFieldSetMapper
package com.apress.springbatch.statement.reader;
import org.springframework.batch.item.file.mapping.FieldSetMapper;
import org.springframework.batch.item.file.transform.FieldSet;
import org.springframework.validation.BindException;
import com.apress.springbatch.statement.domain.Account;
import com.apress.springbatch.statement.domain.Address;
import com.apress.springbatch.statement.domain.Customer;
public class CustomerFieldSetMapper implements FieldSetMapper<Customer> {
public Customer mapFieldSet(FieldSet fieldSet) throws BindException {
Customer customer = new Customer();
customer.setFirstName(fieldSet.readString("firstName"));
customer.setLastName(fieldSet.readString("lastName"));
customer.setTaxId(fieldSet.readString("taxId"));
customer.setAddress(buildAddress(fieldSet));
customer.setAccount(buildAccount(fieldSet, customer));
return customer;
}
private Account buildAccount(FieldSet fieldSet, Customer cust) {
Account account = new Account();
account.setAccountNumber(fieldSet.readString("accountNumber"));
account.setCust(cust);
return account;
}
private Address buildAddress(FieldSet fieldSet) {
Address address = new Address();
address.setAddress1(fieldSet.readString("address"));
address.setCity(fieldSet.readString("city"));
address.setState(fieldSet.readString("state"));
address.setZip(fieldSet.readString("zip"));
return address;
}
}
CustomerFieldSetMapper
has the responsibility of breaking the customer record into three objects:
Customer
,
Address
, and
Account
. As you can see in Listing 10-10, there isn't much to it besides moving the
appropriate fields into the appropriate objects and manually building the relationships. Now that you
