01-30-2007 10:45 AM
<aspect name="contacts:HasLocalisedContact">
<title>Has Localised Contact</title>
<associations>
<child-association name="contacts:localisedContact">
<source>
<mandatory>false</mandatory>
<many>false</many>
</source>
<target>
<class>cms:LocalisedNodeRef</class>
<role>cms:isPropertyOf</role>
<mandatory>false</mandatory>
<many>true</many>
</target>
</child-association>
</associations>
</aspect>
AssocTargetRoleIntegrityEvent.checkAssocQNameRegex:91
RegexQNamePattern rolePattern = new RegexQNamePattern(assocRoleQName.toString());
I've fixed this locally as:
RegexQNamePattern rolePattern = new RegexQNamePattern(assocRoleQName.getNamespaceURI(),assocRoleQName.getLocalName());
The association name does not match the allowed role names:
Association: Association[ class=ClassDef[name={http://researchresearch.com/contacts}HasLocalisedContact], name={http://researchresearch.com/contacts}localisedContact, target class={http://researchresearch.com/cms}LocalisedNodeRef, source role=null, target role={http://researchresearch.com/cms}isPropertyOf]
Allowed roles: RegexQNamePattern[ uri=http://researchresearch.com/cms, localname=http://researchresearch.com/cms ]
Name assigned: {http://researchresearch.com/cms}isPropertyOf
(NB there is another bug here: RegexQNamePattern.toString() prints out the URI of the pattern twice, rather than the URI and the localName! The above should read:
The association name does not match the allowed role names:
Association: Association[ class=ClassDef[name={http://researchresearch.com/contacts}HasLocalisedContact], name={http://researchresearch.com/contacts}localisedContact, target class={http://researchresearch.com/cms}LocalisedNodeRef, source role=null, target role={http://researchresearch.com/cms}isPropertyOf]
Allowed roles: RegexQNamePattern[ uri=http://researchresearch.com/cms, localname=isPropertyOf ]
Name assigned: {http://researchresearch.com/cms}isPropertyOf
)03-07-2008 03:54 AM
03-10-2008 07:49 AM
06-02-2008 04:18 PM
Thanks for posting this.
The association name must match the role name.
06-03-2008 03:19 PM
No (good) reason. It was just a bug that hadn't been hit before: JIRA AR-2157Thanks for posting this.Is there some reason for this?
The association name must match the role name.
06-03-2008 03:30 PM
No (good) reason.Thanks for posting this.Is there some reason for this?
The association name must match the role name.
It was just a bug that hadn't been hit before: JIRA AR-2157
It'll be in the HEAD code if you're feeling lucky.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.