cancel
Showing results for 
Search instead for 
Did you mean: 

Problem uploading a Model

bay96
Champ in-the-making
Champ in-the-making

Hello,

I'm getting an error trying to upload the xml file inside Repository > Data Dictionary > Models:
"Error: The aspect is invalid: {http://www.bcpg.fr/model/designer/1.0}modelAspect"

Anyone XML file returns this error, and there doesn't have reference to modelAspect.

I don't remember if this instance of Alfresco 5.2 (current) had the beCPG module implementation, but the previous instance with Alfresco 5.1 we had the implementation to test and it's a migration from 5.1 to 5.2 of the repositories. But the reference bcpg.fr and modelAspect are found in the beCPG code.

We are using Community - 5.2.0 (r133656-b12) with:

AMP Modules in alfresco.war

Module 'org_alfresco_module_rm' installed in 'tomcat/webapps/alfresco.war'
- Title: Records Management
- Version: 2.6
- Install Date: Wed Sep 13 20:32:04 CEST 2017
- Description: Alfresco Record Management Extension


Module 'alfresco-share-services' installed in 'tomcat/webapps/alfresco.war'
- Title: Alfresco Share Services AMP
- Version: 5.2.0
- Install Date: Thu Dec 22 13:34:49 CET 2016
- Description: Module to be applied to alfresco.war, containing APIs for Alfresco Share


Module 'com.alvexcore.repo.utils' installed in 'tomcat/webapps/alfresco.war'
- Title: Alvex utils [Repo]
- Version: 1.19-SNAPSHOT
- Install Date: Thu Dec 22 13:34:44 CET 2016
- Description: The Maven Alfresco SDK Parent POM exposes the developer features of the Maven Alfresco SDK.


Module 'org.alfresco.integrations.google.docs' installed in 'tomcat/webapps/alfresco.war'
- Title: Alfresco / Google Docs Integration
- Version: 3.0.3
- Install Date: Thu Dec 22 13:34:37 CET 2016
- Description: The Repository side artifacts of the Alfresco / Google Docs Integration.


Module 'project-management' installed in 'tomcat/webapps/alfresco.war'
- Title: Alvex project-management component [Repo]
- Version: 1.30-SNAPSHOT
- Install Date: Thu Dec 22 13:34:31 CET 2016
- Description: The Maven Alfresco SDK Parent POM exposes the developer features of the Maven Alfresco SDK.


Module 'org_alfresco_module_wcmquickstart' installed in 'tomcat/webapps/alfresco.war'
- Title: Web Quick Start
- Version: 5.2.c
- Install Date: Wed Dec 21 12:43:37 CET 2016
- Description: Web Quick Start

AMP Modules in share.war:

Module 'org_alfresco_module_rm_share' installed in 'tomcat/webapps/share.war'
- Title: Alfresco Record Management Share Extension
- Version: 2.6
- Install Date: Wed Sep 13 20:33:06 CEST 2017
- Description: Alfresco Record Management Share Extension


Module 'org.alfresco.integrations.share.google.docs' installed in 'tomcat/webapps/share.war'
- Title: Alfresco / Google Docs Share Module
- Version: 3.0.3
- Install Date: Thu Dec 22 13:35:09 CET 2016
- Description: The Share side artifacts of the Alfresco / Google Docs Integration.


Module 'org_alfresco_module_wcmquickstartshare' installed in 'tomcat/webapps/share.war'
- Title: Web Quick Start Share
- Version: 5.2.c
- Install Date: Thu Dec 22 13:35:06 CET 2016
- Description: Web Quick Start Share Module


Module 'com.alvexcore.share.utils' installed in 'tomcat/webapps/share.war'
- Title: Alvex utils [Share]
- Version: 1.19-SNAPSHOT
- Install Date: Thu Dec 22 13:35:04 CET 2016
- Description: The Maven Alfresco SDK Parent POM exposes the developer features of the Maven Alfresco SDK.


Module 'project-management' installed in 'tomcat/webapps/share.war'
- Title: Alvex project-management component [Share]
- Version: 1.30-SNAPSHOT
- Install Date: Thu Dec 22 13:34:58 CET 2016
- Description: The Maven Alfresco SDK Parent POM exposes the developer features of the Maven Alfresco SDK.

1 ACCEPTED ANSWER

bay96
Champ in-the-making
Champ in-the-making

Fixed, when the beCPG module was implemented, a rule was added inside Models forcing the modelAspect aspect to be added, when beCPG was uninstalled the rule still existed but pointing to an unknown aspect.

View answer in original post

1 REPLY 1

bay96
Champ in-the-making
Champ in-the-making

Fixed, when the beCPG module was implemented, a rule was added inside Models forcing the modelAspect aspect to be added, when beCPG was uninstalled the rule still existed but pointing to an unknown aspect.