[jira] [Resolved] (JCRVLT-283) Error during a copy (RCP)

["Tobias Bocanegra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCRVLT-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Bocanegra resolved JCRVLT-283.
-------------------------------------
    Resolution: Won't Fix

> Error during a copy (RCP)
> -------------------------
>
>                 Key: JCRVLT-283
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-283
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: RCP
>    Affects Versions: 3.1.42
>            Reporter: Adolfo
>            Priority: Blocker
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> I get javax.jcr.PathNotFoundException on a very specific scenario.
> Node Structure :
>  
> {code:java}
> + jcr:content 
>    + par 
>      - sling:resourceType = foundation/components/parsys 
>      + childrenNode 
>        - datatable = (boolean)false 
>        - sling:resourceType = myapp/components/container 
>          + datatable 
>            - text = (String)"<table>...</table>"
>            - sling:resourceType = myapp/components/table{code}
>  
> In this structure, I have a property called "datatable" and child node called "datatable"
> When I do vlt -rcp from one instance to another the following happens:
>  * Fist time it works perfectly
>  * When I run the command again after a node is updated the entire node structure fails to be updated
> I get : 
> ERROR] Error during copy: javax.jcr.InvalidItemStateException: /content/mysite/en/section/news/2018/03/test-monday-001/jcr:content/par/childrenNode/datatable/sling:resourceType
>  
> When vlt is updating the content, it looks like VLT RCP is trying to resolve the path from the property instead from the node.
> In my case, I have more than 60K nodes like this, I can run a groovy script to change the property name and change the code to read the new property, but it should be nice to have a fix to fix the vlt tool.
> Adolfo
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)