[
https://jira.jboss.org/jira/browse/DNA-387?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-387:
-----------------------------------
Added support for writes in limited scenarios (when the nodes being changed are within a
single projection), and addressed a couple of issues related to the handling of UUIDs in
the federation connector. Added more unit tests, verifying the behavior is correct. Also
corrected a few errors in CopyBranchRequest, MoveBranchRequest, and CreateNodeRequest.
Finally, the repository examples (from the Getting Started document) were corrected to use
our JCR implementation. This allowed the parent POM to again include these examples as
subprojects.
Federation connector does not support updates, which are required
when using with the JCR implementation
--------------------------------------------------------------------------------------------------------
Key: DNA-387
URL:
https://jira.jboss.org/jira/browse/DNA-387
Project: DNA
Issue Type: Bug
Components: Connectors, Examples
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
Fix For: 0.4
Our JCR implementation updates the "/jcr:system/dna:namespaces" and
"/jcr:system/nodeTypes" areas as the namespaces and node types change,
respectively. The federation connector doesn't support updates, and using the
federation connector with our JCR results in errors running the repository examples for
the Getting Started guide.
These updates follow a specific and limited pattern: all of the updates are within a
single projection, and in these cases the update requests can be transformed and sent down
to the one connector for the projection. This very limited scenario would go a long way,
and its pretty straightforward.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira