You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/04/27 17:02:31 UTC

[jira] Moved: (OCM-2) Different behaviors between insert and update of a collection

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

Jukka Zitting moved JCR-1895 to OCM-2:
--------------------------------------

          Component/s:     (was: jackrabbit-ocm)
    Affects Version/s:     (was: 1.6.0)
             Workflow: no-reopen-closed, patch-avail  (was: jira)
                  Key: OCM-2  (was: JCR-1895)
              Project: Jackrabbit OCM  (was: Jackrabbit Content Repository)

> Different behaviors between insert and update of a collection
> -------------------------------------------------------------
>
>                 Key: OCM-2
>                 URL: https://issues.apache.org/jira/browse/OCM-2
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            Reporter: Sandrine Raffalli
>
> In the DefaultCollectionConverter in the insert method : if the element has an identifier field it's this field that is taken as the elementJcrName. Else it is the jcrElementName of the collection or the default name.
> In the update method, if the element has an id field and an uuid field, it's the jcrElementName of the collection or the default name that is taken, not the id field.
> In case of insert or update, it must take the same identifier to build the path. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.