OACC Framework v2.0.0-rc.5 Release Notes
Release Date: 2015-11-18 // over 8 years ago-
๐ 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
externalId
to Resource and modifiesgetId()
to returnLong
instead of a primitive - โ adds support for all API methods that take a resource, to handle the alternate
externalId
identifier - 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
withGrant
in all permissions and replaces it withwithGrantOption
for 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()
withexternalId
String parameter - allows one-time setting of alternate resource identifier to an existing resource via the new
setExternalId()
method - adds
externalId
toResource
and modifiesgetId()
to returnLong
instead 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
withGrant
in all permission objects and replaces it withwithGrantOption
for 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.