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

Allow non-components in deployments to access the TransactionSynchronizationRegistry #839

Open
scottmarlow opened this issue Feb 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@scottmarlow
Copy link
Contributor

As per https://jakarta.ee/specifications/transactions/2.0/apidocs/jakarta/transaction/transactionsynchronizationregistry, applications can look up the TransactionSynchronizationRegistry via java:comp/TransactionSynchronizationRegistry unless the application code that needs that is not part of an application component (e.g. in which case no access to java:comp namespace).

This is tracker for introducing a solution. Do any Jakarta EE implementations have a consistent way for non-component code to get access to the TransactionSynchronizationRegistry?

@scottmarlow scottmarlow added the enhancement New feature or request label Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant