batch-api | Jakarta Batch project produces the Batch Specification | Batch Processing library

Please add below in your build.gradle it will go through.

In this particular case, one of the library(jar) from application's WEB-INF/lib directory was causing this issue and the jar is...

Inside of your Injellij double shift (press shift twice) to open the search and type in JDK. Under actions click on switch boot JDK and make sure you have one there if not select one and then click save and restart. hope this works and helps.

SpringApplicationConfiguration is deprecated in favor of SpringBootTest. It was removed in latest spring-boot versions.

You mentioned that you're using Spring Boot 1.4.2 but in fact I see dependencies to 1.5.2 and this is the reason why you can't import it.

I recommend you to use SpringBootTest whenever you want to load spring context in test.

It seem was no intellij idea issues... I've tried to remove my configured datasource trying experiment with default one using embedded db. It works correctly. Next thing that I've done, I used my first datasource configuration but with different step names. That works. Checking DB I've detected that every executed step has COMPLETED status.

Continue investigation... Every my step has COMPLETED status in the DB. By default spring batch doesn't allow execute completed steps.

To make COMPLETED steps handled one more time we can:

• update COMPLETED status in DB with STOPPED or FAILED - that is really hack
• use in step builder function .allowStartIfComplete(true) - the feature of spring batch.

Try adding @Named to your reader, processor and writer classes, and removing src/main/resources/META-INF/batch.xml. This will let CDI to discover batch artifacts as CDI beans and perform dependency injection.

If you just talk about the secure itself, it's a too broad question. In addition, you have many ways to add its security.

First, the environment variables are visible only in the context of the task user, the user account on the node under which a task is executed. And you cannot see them if you connect remotely. It's a secure setting. Then you can set the certificate as you provide, it's also a secure setting. They are the settings of Azure Batch itself.

For more, you can also control the permission to access your batch account. It's also a secure setting. So relatively speaking, it's secure. Hope my opinion will help you understand the security of the batch environment variables.

Just disable Spring Security in your SecurityConfiguration for all requests:

Since you're using Jetty you should be adding spring-cloud-starter-contract-stub-runner-jetty - that way the started WireMock will use the proper container.