Hi,
we probably have the TCK test in place because the spec explicitly
says the map is empty in those cases. see 12.3.2 Event Information.
on the other hand, I don't see a reason why an implementation shouldn't
be allowed to pass more information than required.
I'd say we create an issue for JCR
[
https://issues.apache.org/jira/browse/JCR-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055075#comment-14055075
]
Michael Dürig commented on JCR-3765:
Discussion about adapting the test expectations of
Hi,
Often it would be helpful if observation events would carry node type
information. In Oak we added some initial support for this [1] by adding
the node type and the mixin types of the associated node of an event to
the info map.
In JCR-3765 [2] I suggested to backport this functionality
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.
o Releases
We made the following sta
[
https://issues.apache.org/jira/browse/JCRVLT-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054942#comment-14054942
]
Jukka Zitting commented on JCRVLT-53:
-
I think we should make ~10k orderable child node
