After mapping is executed, you must confirm that the data transformation definition content is valid. When mapping, to avoid errors during validation, take the following points into consideration:
- Execute mapping according to the conditions specified in 6.10 Mapping Conditions.
- Match the occurrence count of the transformation-source nodes at the mapping source to the occurrence count of the transformation-destination nodes at the mapping destination.
- Any complex content element whose minimum occurrence count is set to 2 or greater must be mapped, except when a node, whose minimum occurrence count is 0 occurs as the ancestor.
- Any simple content element (including the any element) whose minimum occurrence count is set to 1 or greater must be mapped.
- Avoid the existence of multiple any elements in the child element of an element with complex contents.
- When mapping a value to a child node of a choice element or to a descendant node, do not define mapping in which multiple child elements occur concurrently or in which no child element occurs.
- When mapping values to multiple child elements of a choice element or to a descendant node, make sure multiple child elements do not occur concurrently.
- When the minimum occurrence count of all child elements of a choice element is set to 1 or greater and the descendant element of one of the child elements is mapped, if you are using a choose node function for that child element, make sure multiple child elements do not occur concurrently.
- Do not define name spaces with URI of xsl and xsi specified in targetNamespace in the mapping--destination transformation-destination node.
- Even when an instance attribute (xsi:type, xsi:schemaLocation, or xsi:noNamespaceSchemaLocation) is defined for the mapping--source transformation-source node, it does not occur in the mapping--destination transformation-destination node.
- When the transformation-source node, in which the instance attribute xsi:nil is defined, is mapped in the transformation-destination node in which the nillable attribute is defined as true, the contents defined in the attribute xsi:nil of the transformation-source node will be applied to the transformation-destination node. In the same way, even when the transformation-source node, in which the instance attribute xsi:nil is defined, is mapped via the choose node function (choose), the contents defined in the attribute xsi:nil of the transformation-source node are applied to the transformation-destination node.
- Do not map from the transformation-source node with the nillable attribute defined to the transformation-destination node where the nillable attribute is not defined.
- When you change following message format while editing the mapping definition, message format before change is displayed. To reflect message format after change, close the target service and start mapping definition again.
- Adding and removing global element
- Changing global element other than root element
- When multiple namespace prefixes are defined for one namespace URL between schema of import destination or include destination, error occurs during verification (including packaging) of mapping definition. Use one type of namespace prefix for one namespace URI.
- When same namespace is defined in different namespace prefixes in message format schema file, root element selection dialog is displayed every time when starting the mapping definition. Do not specify two or more namespace prefixes for one namespace.
- Do not map the following #any element in data transformation definition.
- #any element having #anonymous, #(sequence), or #(choice) in sibling elements
- #any element existing under #(sequence) or #(choice) and having other #(sequence) or #(choice) in sibling element of #(sequence) or #(choice)
- When you specify output destination of node list type custom function to complex contents element, you cannot execute mapping to grandchild node having same dependency relation.
- Points to be considered for node list type custom function is specified in output value of selection function are as follows:
- When mapping destination of Select function is complex contents element and other output value of Select function is "Output a value", you cannot set anything except node list type custom function.
- When mapping destination of Select function is an attribute, you cannot set node list type custom function in the output value of Select function.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.