OACC v2.0.0-rc.5
Pre-release
Pre-release
·
143 commits
to master
since this release
Release date: 2015-11-17
Summary of changes in this release:
- adds support for creating resources with an external id as an alternate resource identifier
- adds
externalIdto Resource and modifiesgetId()to returnLonginstead of a primitive - adds support for all API methods that take a resource, to handle the alternate
externalIdidentifier - resolves and validates resource references passed to the API
- normalizes and validates permissions passed to the API
- deprecates the
getInstance()permission factory methods that take a boolean indicating the grant option and replaces them with dedicatedgetInstanceWithGrantOption()methods - deprecates
withGrantin all permissions and replaces it withwithGrantOptionfor clarity - refactors implementation to remove redundant map traversals and to extract duplicate code blocks
- adds calls to close jdbc statements in tests where it was missing in several instances, and updates Oracle database config properties to use UCP datasource for the tests
- updates test suite for the aforementioned changes
Summary of API changes:
- New feature External id as alternate resource reference
- Prior to this release, OACC exported a single numerical resourceId as the minimal way of coupling, instead of importing a client value, so as to allow the most flexibility in how clients can integrate OACC into their application.
Now OACC allows a client application to specify a single String representation of a globally unique externalId to create and reference resources, so that clients can avoid having to store the resourceId generated by OACC - adds support to provide alternate resource identifier to
createResource()withexternalIdString parameter - allows one-time setting of alternate resource identifier to an existing resource via the new
setExternalId()method - adds
externalIdtoResourceand modifiesgetId()to returnLonginstead of a primitive
- Prior to this release, OACC exported a single numerical resourceId as the minimal way of coupling, instead of importing a client value, so as to allow the most flexibility in how clients can integrate OACC into their application.
- Deprecation deprecates
withGrantin all permission objects and replaces it withwithGrantOptionfor clarity - Deprecation deprecates the
getInstance()permission factory methods that take a boolean to indicate the grant option and replaces them with dedicatedgetInstanceWithGrantOption()methods
Corresponding oacc-db release:
The version of the oacc-db database configuration scripts to be used with this release can be found here.