topic Re: child association trouble in Alfresco Archive

child association trouble

mzaranto — Mon, 25 Jan 2010 15:33:17 GMT

Hi to everyone!I was trying to model a parent-child association, in order to get automatic cascade when deleting or moving the parent. This is the code of the custom model: <child-association name="custom:associationName">

Re: child association trouble

derek — Thu, 28 Jan 2010 13:16:58 GMT

The roles are not important.

Cascade-delete is a function of where a node was created rather than the association itself. If you use your association to create a node, then deleting the node's parent will result in a cascade. If you use your association to link to a secondary parent, then deleting the secondary parent will only remove the association but will not cascade. You will need to write code to listen to the various policies coming from the NodeService, and react accordingly; I'm thinking 'beforeDeleteChildAssociation', in particular.

Re: child association trouble

junieboy — Thu, 04 Feb 2010 02:42:51 GMT

Hi Derek,

Just wanted to make further clarification. Please further elaborate the solution as there seems to be no documentation for this scenario. To implement child association (not peer association) in Java to achieve the cascaded delete functionality, can this be done using Java web services API? If yes, is there any available reference for this?

Also, I believe in your explanation above, you were referring to creating behavior right?

Thanks so much for the information.

Re: child association trouble

derek — Thu, 04 Feb 2010 06:57:07 GMT

Hi,
Delete only cascades along the single child association used to create the child node, known as the primary child association. If you create child associations between pre-existing nodes, then delete will not cascade along them.
Regards

Re: child association trouble

viralshah — Thu, 18 Mar 2010 11:44:01 GMT

How does one create a primary child asociation using the Alfresco Explorer? Right now the explorer gives option to select only content "existing" on any space of Alfresco for child /peer associations. Because of which it looks like the child content does not get deleted even when the parent is getting deleted.

Re: child association trouble

derek — Thu, 18 Mar 2010 11:53:00 GMT

@viralshah

You're correct in that the association created by Explorer will always be secondary i.e. the content selected will not be bound in life to the new parent because it can be shared in this way between several parent nodes. You would have to write your own client extensions if you want to create sub-content (content tied to the parent's lifecycle) through explorer.

Regards

Re: child association trouble

viralshah — Thu, 18 Mar 2010 12:15:57 GMT

Thanks Derek for the confirmation. Is this not a limitation on the Explorer side?
What are the out-of box options available to create such sub-content ? Will we have to create content using the Web services ?

Re: child association trouble

derek — Thu, 18 Mar 2010 13:32:19 GMT

Hi,
When does a potential feature become a limitation? It's not a limitation yet because we haven't been asked for it by enough people.
You can add behaviour to your association to automatically move the selected content under the new parent and thereby bind it's life to that of the new parent; you would still have to create the content first before selecting it. If you want to create it at the time, you'll have to enhance the UI.
You can do anything you want through the APIs.
Regards

Re: child association trouble

viralshah — Tue, 06 Apr 2010 05:15:37 GMT

Hi,
How to create primary child content using the webservices ? It seems that even after creating the child content via webservice ( CMLCreate) and relating it to the parent content is creating a secondary child ( the one which will not get cascade delete).
We tried creatign parentReference with the parent doc ID but it is not working.
Any exmaple code would be useful

Re: child association trouble

cristian — Sat, 08 May 2010 21:26:03 GMT

I've read how to implement primary associations between nodes in the Alfresco reference:


java.lang.Object
  extended by org.alfresco.service.cmr.repository.ChildAssociationRef

ChildAssociationRef

public ChildAssociationRef(QName assocTypeQName,
                           NodeRef parentRef,
                           QName childQName,
                           NodeRef childRef,
                           boolean isPrimary,
                           int nthSibling)

    Construct a representation of a parent — name —-> child relationship.

    Parameters:
        assocTypeQName - the type of the association
        parentRef - the parent reference - may be null
        childQName - the qualified name of the association - may be null
        childRef - the child node reference. This must not be null.
        isPrimary - true if this represents the primary parent-child relationship
        nthSibling - the nth association with the same properties. Usually -1 to be ignored‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍