Compilation Errors

ClosedCompilation validations

  • Having two or more deployable components with the same name in the same file.

  • Having two or more scopes with the same name in the same file.

  • Having two or more TQL queries with the same name in the same file.

  • Having two or more condition functions with the same name in the same file.

  • Having two dependencies with the same name under the same deployable component.

  • Using a variable name in a configuration file condition that is not declared as a global variable in the same file or as a local variable in the dependency to which file configuration file belongs.
  • Using a variable name in a condition function that is not declared as a global variable or as a parameter for the function.
  • Having a cyclic dependency between variables (for example, if the injection statement for the variable VAR_A uses the value from VAR_B and the injection value for VAR_B uses the value of variable VAR_A .
  • Referencing a TQL query that does not exist in the same file.
  • Referencing a scope that does not exist in the same file.
  • Referencing a condition function that does not exist in the same file.
  • Using a variable that does not have a default value in an ignore statement or an alternative expression will result in a compilation error. For more information, see Using Default Values of Variables.

  • If a search expression contains variables with default values, you must handle all cases where any combination of those variables will get their default value. This can be done by either ignoring the expression completely for some of the variables or using alternative expressions. You must have alternative expressions for all combinations of variables that do not appear in the ignore statement. Failing to do so will result in a compilation error. For more information, see Using Default Values of Variables.

  • If a TQL query is used in a <DocumentCILocation> tag, but does not follow these rules:

    • The TQL query must define a path between the deployable component and the configuration document. This path must be simple (no cycles).

    • The TQL query must include the following two end nodes with these specific and case-sensitive names:

      • Deployable – the deployable component CI in the path
      • Configuration_document – the CI in the path that specifies the configuration document
    • Conditions are not permitted on the Deployable and Configuration_document nodes.
    • Cardinalities between all nodes must be 1..1.
    • Only a regular link type is supported. No compounds, joins, or sub-graphs are allowed.

  • If a TQL query is used in a scope, but does not follow these rules:

    • The query node for the deployable component must be called “Deployable” (case-sensitive). The results of this query node are the possible deployable components for the scope.

    • There must be only one other query node in the TQL query (other than “Deployable”). The name of the other query node is not restricted. This node is referred to as the Scope query node.
    • The Deployable and the Scope query nodes are connected with a compound link that contains all available paths between these two nodes.

    • The “Deployable” component represents both consumer and provider components that might be in the same scope. Therefore, the query node CI type must be an ancestor for the consumer and provider deployable CI types.

  • If a Text configuration document contains multiple <ReferenceLocation> tags with different priorities. For more information, see Configuration Document Overrides.