-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch support #2785
Comments
JSR 352 or JBatch is mainly designed to work in a managed EE environment. It requires JPA, JTA naming services etc. to work properly. Helidon is not a full EE container, thus JBatch cannot work correctly.
There is limitation with name resolution in “Stand Alone” mode, thus all bean names should be specified as fully qualified strings. Currently there is an article about this joint technology usage: https://medium.com/helidon/helidon-and-jbatch-2826eec478a2 IBM JBatch version can be upgraded to 2.x after Helidon 3.x is released, since they both will be in “jakarta” namespace. |
The current decision is to focus on joint technology usage. |
See #3895 for doc. |
Investigate if batch support would be a good feature for Helidon.
See Jakarta batch: https://jakarta.ee/specifications/batch/2.0/apidocs/
The text was updated successfully, but these errors were encountered: