[SENTRY-2116] Allow Data Nucleus connection pooling library to be changed via its normal system properties

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.0
• Component/s: Core
• Assignee: Unassigned
• Reporter: Brian Towles
• Created: 04/Jan/18 14:50
• Updated: 04/Jan/18 14:50

Description

Data Nucleus allows multiple different connection pooling libraries to be used, such as DBCP, C3P0, BoneCP, and HikariCP.

Currently we hard code the connection pool library to be used by setting the datanucleus.connectionPoolingType property to be only BoneCP. We are not allowing for any of the custom overrides via system properties to be passed in or used. We do this by passing only override properties into the JDOPersistenceManagerFactory.getPersistenceManagerFactory.

To allow for flexibility during implementation as well as to possibly get around bugs in the default connection pool lib selected we should allow for the end user to be able to set the connection pool via the standard Data Nucleus system properties if necessary.