[ 
https://issues.apache.org/jira/browse/JCRVLT-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050370#comment-18050370
 ] 

Konrad Windszus commented on JCRVLT-833:
----------------------------------------

[~tripod] Protected properties can still be written via JCR Sysview Import, 
this is leveraged e.g. in 
https://github.com/apache/jackrabbit-filevault/blob/c1d3aba606270a016920388e21b6e696e26700fb/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewImporter.java#L1176-L1191.
 However this is done inconsistenly (i.e. only for new nodes not for nodes to 
be updated).

> Consolidate which protected properties to consider during export and import
> ---------------------------------------------------------------------------
>
>                 Key: JCRVLT-833
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-833
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Currently the export ignores certain protected properties: 
> https://github.com/apache/jackrabbit-filevault/blob/c1d3aba606270a016920388e21b6e696e26700fb/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXFormatter.java#L121.
>  During the import only certain protected properties are considered at all 
> (https://github.com/apache/jackrabbit-filevault/blob/c1d3aba606270a016920388e21b6e696e26700fb/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewImporter.java#L142).
>  Currently the set of those two properties are overlapping which is not 
> useful (i.e. some protected properties are never contained in the export but 
> would be considered during import or are contained in the export but are 
> never considered during import).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to