cancel
Showing results for 
Search instead for 
Did you mean: 

running exampleModel

tiofelix
Champ in-the-making
Champ in-the-making
This warning appears: 


WARN  [org.alfresco.repo.node.integrity.IntegrityChecker] Found 2 integrity violations:
The association target multiplicity has been violated:
   Association: Association[ class=ClassDef [ name={my.new.model}sop], name={my.new.model}signOff, target class={http://www.alfresco.org/model/content/1.0}content, source role=null, target role=null]
   Required target Multiplicity: 1..1
   Actual target Multiplicity: 0
The association child multiplicity has been violated:
   Association: Association[ class=ClassDef [ name={my.new.model}sop], name={my.new.model}processSteps, target class={http://www.alfresco.org/model/content/1.0}content, source role=null, target role=null]
   Required child Multiplicity: 1..*
   Actual child Multiplicity: 0


same idea??

Thanks a lot.
1 REPLY 1

gavinc
Champ in-the-making
Champ in-the-making
This is a bug that is rasied in JIRA (I can't get access at the moment though to tell you the issue number).

When a node that has mandatory properties is first created by the web client i.e. before the properties page is displayed, it is in an "incomplete" state, represented by the incomplete aspect applied to the node.

Once all mandatory properties have been added the incomplete aspect is removed. The integrity system will not produce warnings for missing properties when the incomplete aspect is present. The same is not currently happening for associations.

This means when you first create a node that has a mandatory association (like my:sop has) the integrity system will print this warning as it is not checking for the incomplete aspect.

It is not fatal however, and you can continue to use the node as normal.