AMP/AMP model dependency

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

stephenl

Hi,

I'm just wondering if there's a way to have two AMPs and have a custom model in one dependent on a custom model in another? Using Eclipse I have previously built my root amp and have it sat in a dependency folder when I build and deploy my child AMP:

 <build>
        <plugins>
            <plugin>
          <groupId>org.alfresco.maven.plugin</groupId>
          <artifactId>alfresco-maven-plugin</artifactId>
          
          <extensions>true</extensions>
          <executions>
             <execution>
               <id>install-amps</id>
               <goals>
                   <goal>install</goal>
               </goals>
               <phase>package</phase>
             </execution>
          </executions>
          <configuration>
            <ampLocation>libs</ampLocation>
          </configuration>
        </plugin>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

This all seems to work fine for the availability of the webscripts in the root AMP (at run-time) but not for referring to the root model even though it is declared as imported in the child model:

<imports>
  <!– Import Alfresco Dictionary Definitions –>
  <import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d" />
  <!– Import Alfresco Content Domain Model Definitions –>
  <import uri="http://www.alfresco.org/model/content/1.0" prefix="cm" />
  
 <import uri="http://someurl/othercomponent/content/1.0" prefix="rootmodel" /> 
 </imports>
‍‍‍‍‍‍‍‍‍‍

But I always get errors stating that rootmodel cannot be found.

Edit:Basically, what I'm aiming for is the ability to derive a child custom content type from one defined in the root AMP's custom content model.


Thanks a lot.

steven_okennedy

Hi,

Sounds like you're just having problems controlling the order that your amps are being loaded by the system at startup.  The module.properies file has an available option called module.depends.* which allows you to specify that your module depends on (a particular version/minimum version/version range of) another amp.

E.g. module.depends.RootAmp.1.0.0

Have a look at http://docs.alfresco.com/5.1/concepts/dev-extensions-modules-module-properties.html for some examples of what you can do.

Regards

Steven