You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacopo Cappellato (JIRA)" <ji...@apache.org> on 2007/03/25 16:46:32 UTC

[jira] Closed: (OFBIZ-650) persistContentAndAssoc service has problems

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

Jacopo Cappellato closed OFBIZ-650.
-----------------------------------


> persistContentAndAssoc service has problems
> -------------------------------------------
>
>                 Key: OFBIZ-650
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-650
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Bug
>          Components: content
>    Affects Versions: SVN trunk
>            Reporter: Al Byers
>             Fix For: SVN trunk
>
>
> persistContentAndAssoc service has problems. Most serious are called by the change in direction of the "subcontent" direction. See bug OFBIZ-649.
> In the previous scheme, the ContentAssoc.contentId field was used for the child. That make the persistContentAndAssoc (which is a do-all service to persist Content, DataResource and ContentAssoc along with things like ContentPurpose, etc.) easier to program, as the Content.contentId and ContentAssoc.contentId fields overlapped. With ContentAssoc.contentIdTo being the "child" field, it is critical to not let ContentAssoc.contentId and Content.contentId get misused. The answer will be to use the ContentAssocView prefixes everywhere (ie. "ca").

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