Skip to content
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

Use JPA as a default, but also support other systems (like NoSQL databases) #5

Open
stephanpelikan opened this issue Mar 13, 2023 · 0 comments

Comments

@stephanpelikan
Copy link
Collaborator

To validate VanillaBP-annotations in respect to BPMN-versioning all versions of BPMN-files need to be loaded by the adapter. Since Zeebe does not provide information about BPMN already deployed in the past, the adapter stores bundled BPMNs in a repository. They are loaded at startup next to the BPMN currently bundled to fullfill wiring and validation of all versions of BPMN loaded into Zeebe.

At the moment JPA-repositories are used to store and load this information. Since VanillaBP should not stick to JPA any Spring Data crud-repository should be fine. It is likely that many users will use JPA, so the auto-configuration should provide JPA repositories in case those crud-repositories are not provided by the business processing module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant