[
https://issues.apache.org/jira/browse/SLING-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632553#action_12632553
]
Felix Meschberger commented on SLING-665:
-----------------------------------------
> The solution is to add the sling:HierarchyNode mixin to the slingevent:Event
> nodetype
It would probably be better and introducing less dependencies, if the
slingevent:Event node type would just extend from nt:hierarchyNode :
[slingevent:Event] > nt:unstructured, nt:hierarchyNode
...
The sling:HierarchyNode merely exists to turn existing nodes into hierarchy
nodes or to turn nodes of node types we cannot modify into hierarchy nodes on
the fly. For node types we define ourselves, it is probably better to directly
extend from nt:hierarchyNode.
> Two extensions/event tests fail, probably due to sling:folder changes
> ---------------------------------------------------------------------
>
> Key: SLING-665
> URL: https://issues.apache.org/jira/browse/SLING-665
> Project: Sling
> Issue Type: Bug
> Components: Event
> Reporter: Bertrand Delacretaz
>
> mvn clean test in extensions/event says:
> Tests in error:
> testWriteEvent(org.apache.sling.event.impl.DistributingEventHandlerTest)
>
> testWriteEventPlusAppId(org.apache.sling.event.impl.DistributingEventHandlerTest)
> Due to, for example:
> javax.jcr.nodetype.ConstraintViolationException: no definition found in
> parent node's node type for new node: no matching child node definition found
> for {}Event-4711-1221744638373: no matching child node definition found for
> {}Event-4711-1221744638373
> at
> org.apache.jackrabbit.core.NodeImpl.internalAddChildNode(NodeImpl.java:752)
> ...
> at
> org.apache.sling.event.impl.AbstractRepositoryEventHandler.writeEvent(AbstractRepositoryEventHandler.java:282)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
