1
votes

Based on my previous question, I want to specify a part of it which I strongly believe can be a good guide to solve my problem, since the answer to the whole question is probably composed of many parts.

When I define an "association" in an "aspect" (or a type) in Alfresco Content Model, what is actually the "target class"? Could it be another aspect? When I want to associate two aspects as two tables in a regular Database, how this can be done? How can I define the properties in the second aspect? Could someone provide an example of associating two aspects? If the purpose of the association is not that which serves my above requirement, then what does it actually serves?

1

1 Answers

1
votes

When you define an association, its target should be a node type. So node1 is associated to node2 somehow. That node is a valid node (aspect is just a set of properties/assocs over that node2).

Aspect is not a node type, it is merely a few more properties. You can add aspects to types, you can even define mandatory-aspects in type definition. But I think you want to associate node to node.

Now, you want to define an aspect that would be a table in another database? As in, not Alfresco? I believe the proper use case here should be that those tables get a dedicated type, not an aspect.

See what you can read from here and ask more questions on this.

In the mean time, it would help if you clarify a bit what is it that you want to do exactly?