Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <28198075.1187285012105.JavaMail.jira@brutus>
Date: Thu, 16 Aug 2007 10:23:32 -0700 (PDT)
From: "Padraic Hannon (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1067) Referenced beans in an object graph
 should be persisted by the ocm automatically
In-Reply-To: <6922804.1187284893649.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Padraic Hannon updated JCR-1067:
--------------------------------

    Comment: was deleted

> Referenced beans in an object graph should be persisted by the ocm automatically
> --------------------------------------------------------------------------------
>
>                 Key: JCR-1067
>                 URL: https://issues.apache.org/jira/browse/JCR-1067
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jcr-mapping
>    Affects Versions: 1.3.1
>            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.