[GLASSFISH-263] Use a properties file for persistence provider specific properties Created: 15/Feb/06  Updated: 07/Mar/12

Status: Reopened
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 9.0pe
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: tware
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 263

 Description   

Have a property file which look like this:
<provider-class-name1>.<provider-property-A>=<valueA>
<provider-class-name1>.<provider-property-B>=<valueB>
<provider-class-name2>.<provider-property-C>=<valueC>
<provider-class-name2>.<provider-property-D>=<valueD>

This can be loaded in PersistenceUnitLoaderImpl and then we can just pass the
properties specific to a provider in the map paremeter of
createContainerEntityManagerFactory().

Thanks,
Sahoo



 Comments   
Comment by djclarke [ 29/Sep/06 ]

I am unsure of the value of this enhancement. Currently the persistence.xml
provides properties where vendor specific details can be provided. Going forward
as more advanced extensions are supported additional implementation specific
files will be required. I don't see the need to add in yet another file.

If there is some concrete usecases that would warrant this additional file
please provide them and re-open.

Comment by Mitesh Meswani [ 29/Sep/06 ]

This enhancement was filled as a reminder to generalize handling of various
persistence provider in Glassfish. Reopening.
Please note that this is not an issue with Toplink

Comment by Sanjeeb Sahoo [ 07/Mar/12 ]

Assigning to jpa team for taking due action

Generated at Mon Jan 16 11:51:16 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.