You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Padraic Hannon (JIRA)" <ji...@apache.org> on 2007/08/16 19:21:33 UTC
[jira] Created: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
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
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.
[jira] Updated: (OCM-17) Referenced beans in an object graph should
be persisted by the ocm automatically
Posted by "Craig Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OCM-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Schaefer updated OCM-17:
------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1067:
--------------------------------
Attachment: BeanReferenceCollectionConverterImpl.diff
Here is an example implementation for BeanReferenceConverter
> 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
>
>
> 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.
[jira] Commented: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541945 ]
Christophe Lombart commented on JCR-1067:
-----------------------------------------
I would like to suggest to create new converters for this use case but I'm not sure if it is interesting to add them in current code. Anyway, we can maka a vote.
> 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.
[jira] Commented: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542817 ]
Padraic Hannon commented on JCR-1067:
-------------------------------------
Should I create new converters? We are starting to more actively use OCM and we feel this is an important feature to have.
> 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1067:
--------------------------------
Attachment: (was: BeanReferenceCollectionConverterImpl.diff)
> 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.
[jira] Moved: (OCM-17) Referenced beans in an object graph should
be persisted by the ocm automatically
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1067:
--------------------------------
Attachment: ReferenceBeanConverterImpl.diff
Here is an example for ReferenceBeanConverter
> 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.
[jira] Commented: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542962 ]
Christophe Lombart commented on JCR-1067:
-----------------------------------------
After reflexion, I see 2 solutions :
- create new converters
- or apply your patch and set the mapping param : auto-insert, auto-update, auto-delete to false in my case.
I'm going to investigate the second one and review your patch.
Thanks
> 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1067:
--------------------------------
Attachment: BeanReferenceCollectionConverterImpl.diff
Here is an example for BeanReferenceCollection
> 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.
[jira] Commented: (JCR-1067) Referenced beans in an object graph
should be persisted by the ocm automatically
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520314 ]
Padraic Hannon commented on JCR-1067:
-------------------------------------
I have attached to sample diffs.
> 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.