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

Application-managed EMF should map jta-data-source and non-jta-data-source on to internal persistence property names #65

andyjefferson opened this Issue Feb 6, 2017 · 0 comments


None yet
1 participant

andyjefferson commented Feb 6, 2017

If the persistence.xml for an APPLICATION-MANAGED EMF contains jta-data-source and non-jta-data-source then these should be mapped on to

@andyjefferson andyjefferson added the bug label Feb 6, 2017

@andyjefferson andyjefferson added this to the 5.1.0.m1 milestone Feb 6, 2017

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