JSR 352 Spring Batch vs. Java EE
A few questions regarding JSR 352, Spring Batch and Java
1) When would someone use Java to create a JSR-352 batch application via Spring Batch? My initial solution is this would require more Java coding than Spring Batch.
2) Has version 7 implemented Java EE JSR-352? Or did it just come out with a spec and the developers have to implement it? While Spring Batch has implemented it, saving developers programming time?
source to share
In general, this question is subjective (subtext 1) and does not contain fundamental research (subtext 2). I will answer question 2 as it is not subjective. JSR-352 is part of the EE7 specification, so any EE7 compliant application server will implement it. The same is true for any JSR that is part of the EE specification. For an application server to be EE compliant at a given specification level, it must have an implementation of all relevant specification that conveys the appropriate TCKs.
Here's an Oracle technical note describing JSR 352 in Glassfish 4 (the first of many application servers with EE7 complaints).
source to share
A good article can be found at https://blog.codecentric.de/en/2013/07/spring-batch-and-jsr-352-batch-applications-for-the-java-platform-differences/
source to share