jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Moved: (OCM-17) Referenced beans in an object graph should be persisted by the ocm automatically
Date Mon, 27 Apr 2009 15:02:36 GMT

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

Jukka Zitting moved JCR-1067 to OCM-17:
---------------------------------------

          Component/s:     (was: jackrabbit-ocm)
           Issue Type: Bug  (was: Improvement)
    Affects Version/s:     (was: 1.3.1)
             Workflow: no-reopen-closed, patch-avail  (was: jira)
                  Key: OCM-17  (was: JCR-1067)
              Project: Jackrabbit OCM  (was: Jackrabbit Content Repository)

> Referenced beans in an object graph should be persisted by the ocm automatically
> --------------------------------------------------------------------------------
>
>                 Key: OCM-17
>                 URL: https://issues.apache.org/jira/browse/OCM-17
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            Reporter: Padraic Hannon
>         Attachments: BeanReferenceCollectionConverterImpl.diff, ReferenceBeanConverterImpl.diff
>
>
> Currently the BeanReferenceCollectionConverter and ReferenceBeanConverter classes only
persist the UUID of the referenced object. There should either be new converter classes that
cascade down the object graph to ensure all referenced items are created or updated, or the
existing ones should be updated to cascade. 

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


Mime
View raw message