Bug #1871

System properties (like jcr:uuid) are missing

Added by Karsten Dambekalns almost 7 years ago. Updated about 4 years ago.

Status:Resolved Start date:2008-10-27
Priority:Must have Due date:
Assigned To:Karsten Dambekalns % Done:

100%
Category:Property handling
Target version:-

Description

Those need to be exposed

Associated revisions

Revision 33522d86
Added by Karsten Dambekalns over 6 years ago

TYPO3CR:
  • Nodes now expose jcr:uuid and jcr:primaryType, refs #1871
  • Node->hasProperties() thus now returns TRUE hardcoded
  • Node->addNode() now throws an exception when no nodetype is given
  • necessary adjustments to unit tests

History

#1 Updated by Karsten Dambekalns almost 7 years ago

  • Priority changed from Should have to Must have
  • Target version set to 197

#2 Updated by Karsten Dambekalns over 6 years ago

  • Status changed from New to Accepted
  • Assigned To set to Karsten Dambekalns

#3 Updated by Karsten Dambekalns over 6 years ago

This what we should have in a first step, based on the node types defined in the spec and our feature set.

  • jcr:uuid (string) mandatory autocreated protected initialize
  • jcr:primaryType (name) mandatory autocreated
  • jcr:mixinTypes (name) protected multiple autocreated

Since our nodes are always mix:referencable, jcr:mixinTypes will always be present.

#4 Updated by Karsten Dambekalns over 6 years ago

  • % Done changed from 0 to 90

Need to clarify semantics of jcr:mixinTypes property.

#5 Updated by Karsten Dambekalns over 6 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 90 to 100

jcr:mixinType only reflects mixins assigned to a node directly, not inherited ones (like getMixinNodeTypes() does).
Since we don't have support for mixins in that form yet, this is issue is resolved.

#6 Updated by Robert Lemke about 4 years ago

  • Target version deleted (197)

Also available in: Atom PDF