How to call a specific method of a tasklet

Question

In a job context there are an 'method' parameter so a could call directly an tasklet method as said in the documentation "If the tasklet is specified as a bean definition, then a method can be specified and a POJO will be adapted to the Tasklet interface. The method suggested should have the same arguments as Tasklet.execute (or a subset), and have a compatible return type (boolean, void or RepeatStatus)." I declared a bean

    <step id="carregaStep" next="iniciaStep">
        <tasklet ref="atividadesTasklet" method="carregaAtividades"/>
    </step>

I declared a bean that extends Tasklet and I implement an method:

public RepeatStatus carregaAtividades(StepContribution contribution, ChunkContext chunkContext) throws Exception 

But this method is not called.

I try to search an exemplo of use in google, but it's dificult since 'method' in a common word and google cannot search pontuation, like a search for "method=" and "tasklet". Someone could give me an example of use of a method of tasklet?

<bean id="atividadesTasklet" class="br.mypackage.AtividadesTasklet" scope="step" />



public class AtividadesTasklet implements Tasklet{

    public RepeatStatus carregarAtividades(StepContribution contribution, ChunkContext chunkContext) throws Exception {
        return RepeatStatus.FINISHED;   
    }


    @Override
    public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
        return RepeatStatus.FINISHED;
    }   
}


    <step id="carregaAtividadesStep" >
        <tasklet ref="atividadesTasklet" method="carregarAtividades">

        </tasklet>
    </step>

Answer 1

This seems to be a bug. The configuration style you're using:

<tasket ref="myTasklet" method="myMethod"/>

is a shorthand way of configuring the MethodInvokingTaskletAdapter. However, that adapter does not pass on the parameters. If your method takes no parameters it works. I've logged issue BATCH-2397 to track this.

That being said, if you're willing to implement a method that matches the signature of Tasklet#execute, then I'd recommend just implementing the Tasklet interface and skipping this overhead in the first place.