[
https://jira.jboss.org/jira/browse/DNA-269?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-269:
--------------------------------
Attachment: DNA-269.patch
Added patch that implements a writable file system connector. The write capabilities have
some limits. Node ordering and same-name siblings are not supported. Namespaces for
paths (other than the default, empty namespace) are not permitted. Primary types other
than nt:folder, nt:file, dna:resource, and jcr:resource are not permitted. Files with
primary type jcr:resource are effectively converted to files of type dna:resource since
references are not permitted and nt:resource has mix:referenceable as a supertype.
The concept of a maximum path length (FileSystemSource#maxPathLength) was added to limit
the maximum length of the file path of any node that was created. This came about after I
wrote a deeply nested graph to my local filesystem and then found out that Windows
won't let me delete extremely long paths. I defaulted this value to 255 characters,
but some research is needed to determine the correct length for Windows and other
operating systems.
Because of all of the limitations (no arbitrary properties, no namespaces, no node
ordering, no SNS), the canonical writable connector tests don't really pass, so I
added a bespoke test suite for the writable capabilities of the connector. I tried to
make it as inclusive as I could, but other test cases are always welcome.
Add update support to the File System connector
-----------------------------------------------
Key: DNA-269
URL:
https://jira.jboss.org/jira/browse/DNA-269
Project: DNA
Issue Type: Feature Request
Components: Connectors
Affects Versions: 0.3
Reporter: Randall Hauch
Priority: Minor
Fix For: 0.6
Attachments: DNA-269.patch
The File System connector (DNA-34) currently only supports read-access to the files and
folders. Add update support, so a client can create files and folders (not other kinds of
content) on the file system via the graph API and connector.
--
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