In this post we will learn about how to use Spring Batch to read a flat CSV file using FlatFileItemReader
and write to an XML file using StaxEventItemWriter
. We will also witness the usage of JobExecutionListener
and itemProcessor
. Let’s get going.
Following technologies being used:
Let’s begin.
Following will be the final project structure:
We will be reading the flat file (src/main/resources/ExamResult.txt
) and writing to an XML file (project/xml/examResult.xml
)
Now let’s add all contents mentioned in above figure.
Following is the updated minimalistic pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.websystique.springbatch</groupId> <artifactId>SpringBatchCsvToXml</artifactId> <version>1.0.0</version> <packaging>jar</packaging> <name>SpringBatchCsvToXml</name> <properties> <springframework.version>4.0.6.RELEASE</springframework.version> <springbatch.version>3.0.1.RELEASE</springbatch.version> <joda-time.version>2.3</joda-time.version> </properties> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-core</artifactId> <version>${springframework.version}</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-oxm</artifactId> <version>${springframework.version}</version> </dependency> <dependency> <groupId>org.springframework.batch</groupId> <artifactId>spring-batch-core</artifactId> <version>${springbatch.version}</version> </dependency> <dependency> <groupId>org.springframework.batch</groupId> <artifactId>spring-batch-infrastructure</artifactId> <version>${springbatch.version}</version> </dependency> <dependency> <groupId>joda-time</groupId> <artifactId>joda-time</artifactId> <version>${joda-time.version}</version> </dependency> </dependencies> <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> </plugins> </pluginManagement> </build> </project>
Note that here we will be using joda-time api for any date-time processing we might need.
Below is the input file with ‘|’ separated fields whose data we will be converting in XML format.
src/main/resources/ExamResult.txt
Brian Burlet | 01/02/1985 | 76 Jimmy Snuka | 01/02/1983 | 39 Renard konig | 01/02/1970 | 61 Kevin Richard | 01/02/2002 | 59 Rita Paul | 01/02/1993 | 92 Han Yenn | 01/02/1965 | 83
And the mapped POJO with fields corresponding to the row content of above file:
com.websystique.springbatch.model.ExamResult
package com.websystique.springbatch.model; import javax.xml.bind.annotation.XmlElement; import javax.xml.bind.annotation.XmlRootElement; import javax.xml.bind.annotation.adapters.XmlJavaTypeAdapter; import org.joda.time.LocalDate; @XmlRootElement(name = "ExamResult") public class ExamResult { private String studentName; private LocalDate dob; private double percentage; @XmlElement(name = "studentName") public String getStudentName() { return studentName; } public void setStudentName(String studentName) { this.studentName = studentName; } @XmlElement(name = "dob") @XmlJavaTypeAdapter(type = LocalDate.class, value = com.websystique.springbatch.LocalDateAdapter.class) public LocalDate getDob() { return dob; } public void setDob(LocalDate dob) { this.dob = dob; } @XmlElement(name = "percentage") public double getPercentage() { return percentage; } public void setPercentage(double percentage) { this.percentage = percentage; } @Override public String toString() { return "ExamResult [studentName=" + studentName + ", dob=" + dob + ", percentage=" + percentage + "]"; } }
Also note that we have used JAXB annotations in order to map the class properties to XML tags.Since we are using Joda-Time LocalDate
API, we need to tell JAXB about how to perform the conversion.Below is the Adpater class for the same:
com.websystique.springbatch.LocalDateAdapter
package com.websystique.springbatch; import javax.xml.bind.annotation.adapters.XmlAdapter; import org.joda.time.LocalDate; public class LocalDateAdapter extends XmlAdapter<String, LocalDate>{ public LocalDate unmarshal(String v) throws Exception { return new LocalDate(v); } public String marshal(LocalDate v) throws Exception { return v.toString(); } }
FieldSetMapper
is responsible for mapping each field form the input to a domain object
com.websystique.springbatch.ExamResultFieldSetMapper
package com.websystique.springbatch; import org.joda.time.LocalDate; import org.springframework.batch.item.file.mapping.FieldSetMapper; import org.springframework.batch.item.file.transform.FieldSet; import org.springframework.validation.BindException; import com.websystique.springbatch.model.ExamResult; public class ExamResultFieldSetMapper implements FieldSetMapper<ExamResult>{ @Override public ExamResult mapFieldSet(FieldSet fieldSet) throws BindException { ExamResult result = new ExamResult(); result.setStudentName(fieldSet.readString(0)); result.setDob(new LocalDate(fieldSet.readDate(1,"dd/MM/yyyy"))); result.setPercentage(fieldSet.readDouble(2)); return result; } }
ItemProcessor
is Optional, and called after item read but before item write. It gives us the opportunity to perform a business logic on each item.In our case, for example, we will filter out all the items whose percentage is less than 60.So final result will only have records with percentage >= 60.
com.websystique.springbatch.ExamResultItemProcessor
package com.websystique.springbatch; import org.springframework.batch.item.ItemProcessor; import com.websystique.springbatch.model.ExamResult; public class ExamResultItemProcessor implements ItemProcessor<ExamResult, ExamResult>{ @Override public ExamResult process(ExamResult result) throws Exception { System.out.println("Processing result :"+result); /* * Only return results which are equal or more than 60% * */ if(result.getPercentage() < 60){ return null; } return result; } }
Job listener
is Optional and provide the opportunity to execute some business logic before job start and after job completed.For example setting up environment can be done before job and cleanup can be done after job completed.
com.websystique.springbatch.ExamResultJobListener
package com.websystique.springbatch; import java.util.List; import org.joda.time.DateTime; import org.springframework.batch.core.BatchStatus; import org.springframework.batch.core.JobExecution; import org.springframework.batch.core.JobExecutionListener; public class ExamResultJobListener implements JobExecutionListener{ private DateTime startTime, stopTime; @Override public void beforeJob(JobExecution jobExecution) { startTime = new DateTime(); System.out.println("ExamResult Job starts at :"+startTime); } @Override public void afterJob(JobExecution jobExecution) { stopTime = new DateTime(); System.out.println("ExamResult Job stops at :"+stopTime); System.out.println("Total time take in millis :"+getTimeInMillis(startTime , stopTime)); if(jobExecution.getStatus() == BatchStatus.COMPLETED){ System.out.println("ExamResult job completed successfully"); //Here you can perform some other business logic like cleanup }else if(jobExecution.getStatus() == BatchStatus.FAILED){ System.out.println("ExamResult job failed with following exceptions "); List<Throwable> exceptionList = jobExecution.getAllFailureExceptions(); for(Throwable th : exceptionList){ System.err.println("exception :" +th.getLocalizedMessage()); } } } private long getTimeInMillis(DateTime start, DateTime stop){ return stop.getMillis() - start.getMillis(); } }
src/main/resource/spring-batch-context.xml
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:batch="http://www.springframework.org/schema/batch" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/batch http://www.springframework.org/schema/batch/spring-batch-3.0.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-4.0.xsd"> <!-- JobRepository and JobLauncher are configuration/setup classes --> <bean id="jobRepository" class="org.springframework.batch.core.repository.support.MapJobRepositoryFactoryBean" /> <bean id="jobLauncher" class="org.springframework.batch.core.launch.support.SimpleJobLauncher"> <property name="jobRepository" ref="jobRepository" /> </bean> <!-- ItemReader reads a complete line one by one from input file --> <bean id="flatFileItemReader" class="org.springframework.batch.item.file.FlatFileItemReader" scope="step"> <property name="resource" value="classpath:examResult.txt" /> <property name="lineMapper"> <bean class="org.springframework.batch.item.file.mapping.DefaultLineMapper"> <property name="fieldSetMapper"> <!-- Mapper which maps each individual items in a record to properties in POJO --> <bean class="com.websystique.springbatch.ExamResultFieldSetMapper" /> </property> <property name="lineTokenizer"> <!-- A tokenizer class to be used when items in input record are separated by specific characters --> <bean class="org.springframework.batch.item.file.transform.DelimitedLineTokenizer"> <property name="delimiter" value="|" /> </bean> </property> </bean> </property> </bean> <!-- XML ItemWriter which writes the data in XML format --> <bean id="xmlItemWriter" class="org.springframework.batch.item.xml.StaxEventItemWriter"> <property name="resource" value="file:xml/examResult.xml" /> <property name="rootTagName" value="UniversityExamResultList" /> <property name="marshaller"> <bean class="org.springframework.oxm.jaxb.Jaxb2Marshaller"> <property name="classesToBeBound"> <list> <value>com.websystique.springbatch.model.ExamResult</value> </list> </property> </bean> </property> </bean> <!-- Optional ItemProcessor to perform business logic/filtering on the input records --> <bean id="itemProcessor" class="com.websystique.springbatch.ExamResultItemProcessor" /> <!-- Optional JobExecutionListener to perform business logic before and after the job --> <bean id="jobListener" class="com.websystique.springbatch.ExamResultJobListener" /> <!-- Step will need a transaction manager --> <bean id="transactionManager" class="org.springframework.batch.support.transaction.ResourcelessTransactionManager" /> <!-- Actual Job --> <batch:job id="examResultJob"> <batch:step id="step1"> <batch:tasklet transaction-manager="transactionManager"> <batch:chunk reader="flatFileItemReader" writer="xmlItemWriter" processor="itemProcessor" commit-interval="10" /> </batch:tasklet> </batch:step> <batch:listeners> <batch:listener ref="jobListener" /> </batch:listeners> </batch:job> </beans>
As you can see, we have setup a job with only one step. Step uses FlatFileItemReader
to read the records, itemProcessor
to process the record & StaxEventItemWriter
to write the records. commit-interval
specifies the number of items that can be processed before the transaction is committed/ before the write will happen.Grouping several record in single transaction and write them as chunk provides performance improvement. We have also shown the use of jobListener
which can contain any arbitrary logic you might need to run before and after the job.
Create a Java application to run the job.
com.websystique.springbatch.Main
package com.websystique.springbatch; import org.springframework.batch.core.Job; import org.springframework.batch.core.JobExecution; import org.springframework.batch.core.JobExecutionException; import org.springframework.batch.core.JobParameters; import org.springframework.batch.core.launch.JobLauncher; import org.springframework.context.ApplicationContext; import org.springframework.context.support.ClassPathXmlApplicationContext; public class Main { @SuppressWarnings("resource") public static void main(String args[]){ ApplicationContext context = new ClassPathXmlApplicationContext("spring-batch-context.xml"); JobLauncher jobLauncher = (JobLauncher) context.getBean("jobLauncher"); Job job = (Job) context.getBean("examResultJob"); try { JobExecution execution = jobLauncher.run(job, new JobParameters()); System.out.println("Job Exit Status : "+ execution.getStatus()); } catch (JobExecutionException e) { System.out.println("Job ExamResult failed"); e.printStackTrace(); } } }
Running above program as java application, you will see following output
ExamResult Job starts at :2014-08-03T15:26:54.770+02:00 Aug 3, 2014 3:26:54 PM org.springframework.batch.core.job.SimpleStepHandler handleStep INFO: Executing step: [step1] Processing result :ExamResult [studentName=Brian Burlet, dob=1985-02-01, percentage=76.0] Processing result :ExamResult [studentName=Jimmy Snuka, dob=1983-02-01, percentage=39.0] Processing result :ExamResult [studentName=Renard konig, dob=1970-02-01, percentage=61.0] Processing result :ExamResult [studentName=Kevin Richard, dob=2002-02-01, percentage=59.0] Processing result :ExamResult [studentName=Rita Paul, dob=1993-02-01, percentage=92.0] Processing result :ExamResult [studentName=Han Yenn, dob=1965-02-01, percentage=83.0] ExamResult Job stops at :2014-08-03T15:26:54.891+02:00 Total time take in millis :121 ExamResult job completed successfully Aug 3, 2014 3:26:54 PM org.springframework.batch.core.launch.support.SimpleJobLauncher run INFO: Job: [FlowJob: [name=examResultJob]] completed with the following parameters: [{}] and the following status: [COMPLETED] Job Exit Status : COMPLETED
You can see that we have processed all input records. Below is the generated XML file found in project/xml folder
<?xml version="1.0" encoding="UTF-8"?> <UniversityExamResultList> <ExamResult> <dob>1985-02-01</dob> <percentage>76.0</percentage> <studentName>Brian Burlet</studentName> </ExamResult> <ExamResult> <dob>1970-02-01</dob> <percentage>61.0</percentage> <studentName>Renard konig</studentName> </ExamResult> <ExamResult> <dob>1993-02-01</dob> <percentage>92.0</percentage> <studentName>Rita Paul</studentName> </ExamResult> <ExamResult> <dob>1965-02-01</dob> <percentage>83.0</percentage> <studentName>Han Yenn</studentName> </ExamResult> </UniversityExamResultList>
Only the records which are meeting specific condition ( percentage >=60) are included here, thanks to itemProcessor filtering logic.
That’s it.
If you like tutorials on this site, why not take a step further and connect me on Facebook , Google Plus & Twitter as well? I would love to hear your thoughts on these articles, it will help improve further our learning process.
In this post we will be developing a full-blown CRUD application using Spring Boot, AngularJS, Spring Data, JPA/Hibernate and MySQL,…
Spring Boot complements Spring REST support by providing default dependencies/converters out of the box. Writing RESTful services in Spring Boot…
Being able to start the application as standalone jar is great, but sometimes it might not be possible to run…
Spring framework has taken the software development industry by storm. Dependency Injection, rock solid MVC framework, Transaction management, messaging support,…
Let's secure our Spring REST API using OAuth2 this time, a simple guide showing what is required to secure a…
This post shows how an AngularJS application can consume a REST API which is secured with Basic authentication using Spring…
View Comments
I've not seen such a great working tutorials. Much better to learn. Thanks for doing needful.
Hi Prateek,
Thanks for the nice comments.
This piece is absolutely amazing! Lots of thanks to websystique!
Hi Michael, Glad it was helpful.