Version object which has child-association via Aspect

[colindstephenso]

I am creating an object and attaching an aspect to it through a custom webscript.  This aspect contains a single property and a child association of cm:content.  When I modify the object, I create a new txt object which I link to the child-association.  When I view object, the child association (attached via the aspect) is available.  I can also verify this through the javascript debugger.

If I delete the object, the child-associated content gets deleted as well, so the relationships are working as expected.  Now, if I enable versioning and look at the object through version history, I see, through the javascript debugger that the my aspect is attached to the versioned object, but it does not maintain the child association.  The aspect property it preserved as expected.

Is there something else I need to do when versioning documents which contain a child-association via an aspect so that its respected through the version store?

Thanks in advance.

[pucfg1]

Hi all,

I have observed the same behavior.
When I inspect a versioned document using Alfresco Node Browser(in Version2Store store)
the custom aspect is present(in aspects table) but there is no aspect`s associations - tables children and associations are empty.

The same document(the most recent one in the SpacesStore, not in the version store) has both aspect and aspect association.
When I inspect versioned documents with child associations(not aspect associations) the child node is available in children table.

In my requirement each version of document should has different version of aspect child association.
Could anyone explain how aspect associations are versioned in Alfresco?

Thanks in advance !

[colindstephenso]

This need has raised it's head again.  Does anyone have a solution on versioning an object which has a child association?  I need to parent and child to be versioned so as to maintain true version history,

Cheers,
Colin.