-
Hi Chudak,
I am using Spring Batch 1.1.2.
My biggest question is how to clean up the 'prototype' data beans used by org.springframework.batch.item.file.mapping.BeanWr apperFieldSetMapper
Here is my config
Code:
<bean id="dataSupplierFieldSetMapper"
class="org.springframework.batch.item.file.mapping.BeanWrapperFieldSetMapper">
<property name="prototypeBeanName" value="dataSupplier" />
</bean>
<bean id="dataSupplier"
class="com.company.DataSupplier"
scope="prototype" />
<bean id="dataSupplierFixedLengthLineTokenizer"
class="org.springframework.batch.item.file.transform.FixedLengthTokenizer">
<property name="names" value="cobolSupplierCode,name,oracleSupplierSiteCode,title,firstName,middleName,lastName,department,areaCode,contactPhone,email,oracleOperatingUnitName,eol" />
<property name="columns" value="1-6,
7-31,
32-51,
52-71,
72-91,
92-111,
112-131,
132-151,
152-171,
172-191,
192-241,
242-291,
292-1500" />
</bean>
I will run the profiler and I hope I get lucky to solve this.
Cheers
Vito
-
Are you suggesting there is a memory leak? If so we would like to have a JIRA so we can track it.
By the way, your dataSupplier bean doesn't need to be a bean definition at all because BeanWrapperFieldSetMapper can create beans with a default constructor by itslef.
-
