Renaming files one at a time with MultiResourceItemReader

[jftardif]

Hi all,

Do anybody know how to rename files one at a time when using a MultiResourceItemReader. I mean, I want to process all the files in a specific directory but I want to rename each file when it has been processed.

Directory content example:
File1.xml
File2.xml
File3.xml

After the first file has been processed:
File1.xml.processed
File2.xml
File3.xml

Is it possible to do that?

Thanks for your help!

[lucasward]

The only way I can think to do that would be to flag the files after the step is complete, using a StepExecutionListener. I can't think of a good way to do that while the step is still executing though.

[ballistic_realm]

Hi Lucas

So you mean in the afterStepexecution method, we flag the files ? And how do we access the file names from the stepexecution ? Is it by injecting the resources into that class ?

And also, because we are using MultiResourceReader, how can we reliably flag which file that has been processed ? Do you mean just flag all the files within that directory in the afterStepexecution method?.

[DHGarrette]

ballistic_realm,

The way I've done it in the past is this:

Create a wrapper class for your FlatFileItemReader. The wrapper can be used by itself, or set as the delegate of the MultiResourceItemReader.

You'll have to store the resource in the wrapper:

public void setResource(Resource resource) {
	this.resource = resource;
	this.delegateReader.setResource(resource);
}

The wrapper's read() will do the following:

public Object read() throws Exception {
	Object o = this.delegateReader.read();
	if (o == null) {
		//
		// After the last item is read
		//
		this.renameResource(this.resource);
	}
	return o;
}

If you want to do the renaming afterwards, then you'll store the resource to a list in read(), implement StepExecutionListener, and perform the rename in afterStep().

If you want to do the renaming as a separate step, then you'll store the resource to a list in the stepExecution.getJobExecution().getExecutionContex t() in afterStep(). That way you can access it in a later step.

[ballistic_realm]

Hi DHGarrette

your solution works perfectly

thanks for the input

regards

ballistic_realm