Search:

Reading the documentation for the CommandLineJobRunner I'm wondering, why you would restart a JobExecution rather than a JobInstance?

E.g. I have a couple of failed JobExecutions for one...

Unfortunatly the call to the SAP-system returns a whole table (list of items) with ONE call. So the regular ItemReader such JdbcCursorItemReader is not appropriate.

I tried it with a custom reader...

I'm stucked with a probably little problem, I'd be glad if someone got an idea how to solve it:

One step of my batch job is supposed to do
- read a table from a SAP-connection
- do some business...

It has to be correctly spelled because I'm able to follow this link in Eclipse by clicking ctrl+link. But obviously my Eclipse doesn't follow this link.

Anyway, here is my beans-definition:

...

I'm having the same problem here. Everything was alright until I changed from 1.1 to 2.0 and used the new namespace introduced in Spring 2.0.

When using new xml-tags or attributes Eclipse now...

Thanks for the information!

But then the doc is not up to date because I found this in 6.3.1:



<job id="ioSampleJob">
<step name="step1">
<tasklet reader="fooReader"...

I just try to migrate from Spring Batch 1.1 to 2.0.0

When I try to use the property "reader" for the element "tasklet" as in the examples I get an XML-parsing error which says:

Attribute...