...
Warning | ||
---|---|---|
| ||
It is very important that the SPI doesn't expose any database implementation for example database ID's |
Description | Details | Decisions | |
---|---|---|---|
1 | Assume flat attributes (no complex data types) but data could be stored as json object in SPI impl. for convenience/PoC | ||
2 | SPI Implementation NOT using Model (service) current ENM SPI does! | ||
3 | Are we going to have XPath/query builder? |
| |
4 | Having a fluent interface in my opinion would be way more intuitive and practical. E.g. //AND of two restrictions Restriction and(Restriction firstRestriction, Restriction secondRestriction) //OR of two restrictions Restriction or(Restriction firstRestriction, Restriction secondRestriction) //NOT of a restriction Restriction not(Restriction restriction) This will give any user of the API an intuitive way to build a complex query and the developer a tree to navigate and translate to SQL (or any other query language). A developer could do something the likes of myQuery.setRestriction(restriction1.and(restrcition2).and(restriction3)) | ||
5 | When do we get attributes? | How do control how many attributes we get back? Maybe we dont need this because we dont have complex data attributes | We have the following options
|
6 | Should we use the name node or fragment? | DataNode /Node | |
7 | Do we want to split the interface? | Maybe we could just have a 3 Alternatives
| peristenceStore.addChild(parentDataObject, childDataObject)
We will not have a querybuilder in SPI but the SPI will have to understand the query. API - construct the CPS path SPI - deconstruct it and convert it into a query From an end user perspective anchor and fragment are different - we should separate them CpsAdmin Interface will handle the datastore and anchor access control? extend the CpsAdmin Module SPI - responsible for handling modules and module sets |
QueryBuilder - responsibility of API
ENM SPI Study
Details about the ENM SPI can be found here: Spike
...
Proposed Future Implementation of CPS SPI
...
DataStore SPI
Name | Definition | Capabilities | |||
---|---|---|---|---|---|
1 | SimpleDataObjectDataStoreObject | Provides the basic information needed to access an object. |
| ||
2 | DataPersistenceServicePersistenceStore | Adding functionality for handling attributes
Gets the persistence layer object without any layers of decoration. If the innermost object is not a persistence layer object then a suitable exception will be thrown. |
Passes the attributes supplied by the user for a new persistence object so that they may be verified as required.
Initializes the attributes for a new persistence object. This method should be invoked when creating a new persistence object rather than using setAttributes() as it will have different behavior, namely:
Gets the values for the attributes which have been specifically set on this object. This includes attributes which:
Note that an attribute may have been specifically set to null so the values returned in the map may contain nulls.
Determines if the supplied attribute has been specifically set (includes attributes which were set to null).
Gets all of the attribute names available in this persistence object.
Unsets the values of the supplied attributes.
| 3 | FragmentObject |
4 | DataspaceObject | Create a simple CPS Dataspace Object |
|
...
|
CpsAdmin SPI
Name | Definition | Capabilities | |
---|---|---|---|
1 | DataspacePersistenceService |
|
...
| ||||||
| ||||||
| ||||||
| 1||||||
2 | FragmentPersistenceServiceAnchorPersistenceService | getByCpsPath
| createNode
| associateNodeToAnchor
| associateAnchorToDataspace
|
Module SPI
Name | Definition | Capabilities | |
---|---|---|---|
1 | ModulePersistenceService | Adding functionality for handling attributes |
Remove all associations of this persistence object.
Retrieves the namespace of the type of object the type query is to target.
|
2 | BasicModuleObject | Create a simple CPS Module Object |
|
Query SPI
Definition
Capabilities
QueryService
Service responsible for dealing with query related features of CPS.
- execute
Executes the query and presents the result as an iterator of objects queried for.
- executeCount
Executes the query and presents the result as a count of how many instances are matched against the query.
Note: because of database limitations, at this moment this method is not optimized.
- executeDeletion
Deletes all matching objects and where appropriate deletes any children.
- getSchemaNodeIdentifier (Type)
Retrieves the type of object that the type query is to target.
QueryPathService
Service responsible for dealing with path query related features
- executePathQuery
executes the path query against the db. returns a list of type Object.
- getTargetObjects
Executes the query ands gets the result as an iterable of 'full' objects queried.
getNodesByPathForAnchor
getNode
queryNodes
getNodeBySchemaNodeIdentifier
- pathRestriction
- getRestriction
Gets the restriction used in the query criteria, including any internal restrictions added in addition to those set by the user.
- getAttributeName
Retrieves the name of the attribute that the restriction is.
SimpleRestriction
Creates a simple restriction (e.g. compare one field to one value).
negate
getAttributeName
getAttributeValue
getSimpleExpressionOperator
toString
PartialMatchRestriction
Implementation of the partial match restriction and not match restriction.
negate
getRestrictionType
getMatchConditionType
getAttributeName
isNegated
getStringToMatch
toString
LogicalRestriction
Implement logical restriction (AND/OR) and the negation of this logical restriction.
negate
getRestrictionType
getRestrictionList
getLogicalOperator
isNegated