Development tools : Web services tooling : Limitations and known issues : Data name mapping issue
  
Data name mapping issue
Background
In self defined operation generation, if refer global data dictionary for data mapping, it will generate dirty data definition in operation in following scenario, while those dirty data won't impact the SDO execution.
Issue details
Suppose we have a WSDL definition like the following:
This graphic is described in the surrounding text.
The type mapping definition is ready and the related UDTT type is also defined in type.xml:<type-mapping xsdName="InnerBean" bttName="InnberBeanType"/>
In global data dictionary, there is a data with the 'InnerBeanType'.
This graphic is described in the surrounding text.
During the tooling execution, we do the name mapping for the field 'o1' of OutterBean (the type of 'o1' is 'InnerBean')
This graphic is described in the surrounding text.
Then the generation result will be:
This graphic is described in the surrounding text.
But if we do the name mapping for both 'o1' and 'input2' (both of them are of type 'InnberBean' in XSD)
This graphic is described in the surrounding text.
Then the generation result will be:
This graphic is described in the surrounding text.
See also
Limitations and known issues