User/client passes in an dataspace name, anchor name and an cpsPath for the object

The cpsPath should NOT include module name/namespace/revision details

The cpsPath should be identical to the xpath property stored in the DB

Implement all layers for get-by-cpsPath (e.g '/bookstore')

1. REST API
2. Java API
3. DB SPI

return single object with its attributes (under the correct Anchor)

All descendant of the object will be returned too (a separate user story to optionally NOT return any descendant or only a certain depth will be done later)

handle not found exception

Depending on what works out of the box add test cases to proof the specific functionality supported (DB integration tests? If some specific (basic) yang feature doesn't work add a bug on that instead. Depending on the requirement for E2E slicing use case we will decide the priority of those bugs

1. A Yang container
2. A keyed Yang list element
3. Descendants (of a container)
4. Standard Yang leaves
5. leafLists