spring-cloud-task and spring-data-jpa auto configuration cannot be used together

[Ramblurr]

There is a conflict when using spring-cloud-task and spring-data-jpa together with the most simple auto configuration.

spring-cloud-task instantiates a transactionManager, but it is not of the type JpaTransactionManager that spring-data-jpa expects..

The workaround is to provide your own JpaTransactionManager.

Here is a minimal sample project showing the problem including the workaround:

https://github.com/Ramblurr/spring-data-task-conflict

[cppwfs]

In this case You would want to create your own TaskConfigurer to return the transaction manager you want. Which can be found here: https://github.com/spring-cloud/spring-cloud-task/blob/master/spring-cloud-task-core/src/main/java/org/springframework/cloud/task/configuration/TaskConfigurer.java You can use the the DefaultTaskConfigurer as a guide.

[mminella]

As @cppwfs notes, this use case is addressed by the existing functionality. I'm closing this unless there is some other aspect that is missing.

[Ramblurr]

Fair enough, I see the TaskConfigurer can be used to provide the custom transaction manager.

But shouldn't this gotcha with spring-data be documented somewhere? I can't imagine using spring-data and spring-cloud-task is far from ordinary. Just a few words somewhere pointing out that you can't use spring-data and cloud-task out of the box together would have saved me an hour or so.

[cppwfs]

I agree. Opened an issue to address this: #272.