Article ID: 119961, created on Feb 3, 2014, last review on Apr 27, 2014

  • Applies to:
  • APS 2.x

Symptoms

In APS1 I could define services hierarchy in APP-META.xml:

<service id="top-service">
<...>
    <service id="sub-service">
    <...>
    </service>
    <...>
</service>

How it should be done in APS2?

Resolution

APS2 services are now linked based on relations node specified in schema of each resource

For example for main customer service (aka tenant) to be able to read settings from main provider service (aka globals) there should be the following relations:

  • in globals.schema:

    "relations": {
        "tenant": {
    "type": "http://application.com/tenant/1.0",
    "collection": true
        }}
    
  • in tenant.schema:

    "relations": {
    "globals": {
      "type": "http://application.com/globals/1.0",
      "required": true,
      "collection": false
    }}
    

70bf700e0cdb9d7211df2595ef7276ab 717db81efe94e616312b74fb03a5d474

Email subscription for changes to this article
Save as PDF