Feature #1291
Make it possible to suggest an identifier for a new node
| Status: | Resolved | Start date: | ||
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Node handling | |||
| Target version: | - |
Description
To make the gap between a DDD domain object eventually having it's own UUID already and the CR persisting that object as a node, it should be possible to suggest an identifier to the CR when creating a node.
- check what the spec says
- think about a clean & lean way of doing this
- implement :)
Related issues
Associated revisions
PHPCR:
- added third optional parameter to Node.addNode(), relates to #1291
- Node.addNode() now accepts a third optional parameter allowing to suggest an identifier for the new node, fixes #1291
- Node.addNode() now uses the requested nodetype for relative paths pointing away from the current node
History
#1 Updated by Karsten Dambekalns almost 7 years ago
- Status changed from New to Accepted
- Assigned To set to Karsten Dambekalns
#2 Updated by Karsten Dambekalns almost 7 years ago
Ok, the spec says (basically), what an identifier must conform to and when it is needed. It does not prohibit suggesting one, although it does of course not have such functionality.
#3 Updated by Karsten Dambekalns almost 7 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1152.