Home
Categories
Dictionary
Glossary
Download
Project Details
Changes Log
What Links Here
FAQ
License

Service Merger configuration


    1  Schema
    2  Structure
       2.1  outputService
       2.2  inputService
       2.3  data
    3  Example
    4  See also

The XML file for the Service Merger specifies the correspondance between output datas and inputs datas.

Schema

The schema is: merger.xsd.

Structure

The root contains:
  • " outputService" elements which specify the output Services which will have datas set by other datas from input Services

outputService

The "outputService" element specifies a service for which the Service Merger is a provider, for which some datas will be set by other datas from services for which the Service Merge is a subscriber. This element has only one attribute:
  • "name": the name of the Service. Note that it must be a Service for which the Service Merger is a provider


This element contains the following children elements:
  • " inputService" which define the services for which the Service Merge is a subscriber for which some datas will be used to set the datas values for the outputService
  • " data" which define the datas which will be set int the output Service and which data will be used to set this data from one of the input Service


Example:
      <mergerConf>
         <outputService name="output1">
      ...
         </outputService>
      </mergerConf>

inputService

The "inputService" element specifies a service for which the Service Merger is a subscriber, for which some datas will be used to set set datas of the outputService. This element has only one attribute:
  • "name": the name of the Service. Note that it must be a Service for which the Service Merger is a subscriber


Example:
      <inputService name="input1" /<

data

The "data" element specifies a data which belong to the outputService which will be set by another data for one of the inputService. This element has the following attributes:
  • "name": the name of the data. Note that it must be a data which belong to the outputService
  • "fromService": the name of the inputService which will be used to set the data. Note that his service must have been defined in one of the inputService elements, and of course it must be a Service for which the Service Merger is a subscriber
  • "fromData": the name of the inputService data which will be used to set the data. Note that the data must belong to the fromService" Service


Example:
      <data name="info11" fromData="info31" fromService="input1" /<

Example

      <mergerConf>
         <outputService name="output1" >
            <inputService name="input1" />
            <inputService name="input2" />
            <data name="info11" fromData="info31" fromService="input1" />
            <data name="info12" fromData="info42" fromService="input2" />
         </outputService>
      </mergerConf>

See also


Categories: builtin-applis

Copyright 2017-2020 Dassault Aviation. All Rights Reserved. Documentation and source under the LGPL v3 licence