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

Switch database query building to JTA rather than RESOUCE_LOCAL #81

Open
kevin-mcgoldrick opened this issue Oct 17, 2019 · 2 comments
Open

Comments

@kevin-mcgoldrick
Copy link
Collaborator

Ideal State

The current data_access module is built with a lot of custom database query building content. While this is a tightly controlled model of database access, I feel like this interface could be handed over to a JTA provider for better longterm support.

@samuelbchase
Copy link

I'm interested in looking into this. I've done some research on the goal end state, and it looks like for each instance of embedded RESOURCE_LOCAL entity managers we want to switch to a JTA model (Container injects the entity manager)?

@kevinmcgoldrick
Copy link
Collaborator

kevinmcgoldrick commented Oct 5, 2023 via email

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

No branches or pull requests

3 participants