I am trying to do a SystemView Import, and have a UUID created if the node
does not already exist. I use an XSLT to x-form my XML into the proper
SystemView, and include a node for jcr:uuid. If this value is empty, the
JCR throws an exception. If I remove the jcr:uuid node, the JCR imports the
Angela Schreiber wrote:
but that's a different story isn't it? i was talking about the
compliance class (and the method set).
Probably. I just wanted to make sure that no time is spent on something
that is broken in the spec...
RFC 3253 defines a separate behaviour for version-controlled
[
https://issues.apache.org/jira/browse/JCR-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513577
]
Shane Preater commented on JCR-537:
---
I am also seeing this error when trying to remove the version mixin from a node.
hi
Clarifying: the difference between a collection and a non-collection
with respect to WebDAV versioning is that the version-controlled state
of a collection *additionally* includes the binding-set (for the
members), but not the members itself.
jup... and that's currently missing.
Hm,
Angela Schreiber wrote:
...
leading to the question: will it cause problems if the dav-client
can 'see' dav VersionHistoryResources and VersionResources that
don't have a corresponding versionable dav resource? or would that
be an negligible inconsistency?
...
That shouldn't be a problem,
