In order to use this module, additional exceptions need to be added to the security policy.
The following should be no problem to add:
(java.util.PropertyPermission "hikaricp.configurationFile" "read")
(java.util.PropertyPermission "com.zaxxer.hikari.*" "read")
However, once these permissions are added to the policy (Mendix\\modeler\runtemplates\deployment\data\security.policy) another permission is required.
Due to the fact that the once a datasource is created with no name, a random number is generated and updated globally. As a result a read/write * is required. This can be solved by adjusting the JdbcConnectionManager with the attached version.
Changes are
48 - passing the parameter of the connPoolKey to the function createHikariDataSource
74 - extending the definition of the function createHikariDataSource with an integer parameter
76 - inserted the setting of the poolName of the dataSource to prevent the generation of the poolnumber globally.
In order to use this module, additional exceptions need to be added to the security policy.
The following should be no problem to add: (java.util.PropertyPermission "hikaricp.configurationFile" "read") (java.util.PropertyPermission "com.zaxxer.hikari.*" "read")
However, once these permissions are added to the policy (Mendix\\modeler\runtemplates\deployment\data\security.policy) another permission is required.
java.security.AccessControlException / access denied ("java.util.PropertyPermission" "*" "read,write")
Due to the fact that the once a datasource is created with no name, a random number is generated and updated globally. As a result a read/write * is required. This can be solved by adjusting the JdbcConnectionManager with the attached version.
Changes are
See pull request #5 for updated code.