-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add JNDI server support #25
Comments
I think there's some ways to do the integration without JNDI. Specifically, overriding the Bittronix integration in hibernate to not use JNDI to look up the user transaction. This would be true of other JTA impls out there. Narayana seems to be notorious for its use of JNDI so I'd be cautious to bring it in. |
You're right, we could do without JNDI, but it may imply that we'll have to support specific integration should we have multiple JPA impl support later. |
Also not true. We can implement |
Antoine and I spoke about this. We agreed, the best solution is to provide a "simple" JNDI like service for binding beans, probably just named beans, in a look up. |
JNDI server is mandatory if we want to add feature like #24 and JTA support.
The text was updated successfully, but these errors were encountered: