Major Description
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").