[JPA_SPEC-54] Clarify behavior of RESOURCE_LOCAL EMF instantiated by container Created: 12/Apr/13  Updated: 12/Apr/13

Status: Open
Project: jpa-spec
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Mitesh Meswani Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

It is possible to inject/lookup an EMF that is derived from a RESOURCE_LOCAL pu. For such EMFs, we need to clarify the behavior for following:

1. Should we disallow specifying jta-data-source

2. If the persistence.xml specifies both non-jta-datasource and javax.persistence.jdbc.* properties, which one should take precedence?

3. If the persitence.xml specifies no database connection information, should we default non-jta-datasource?

3. If the persistence.xml just specifies javax.persitsence.jdbc.* properties, what should be the behavior? Should we still default non-jta-datasource


Generated at Fri Mar 27 22:24:34 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.