Currently when VDB is written, the <ComponentTypes> section in the ConfigurationInfo.def file defines the component types for all the bindings defined. However the number of properties defined for each component type include all the properties in hierarchy of that Component Type. Which verbose and confusing.

For example in Configuration.XML file a "Oracle Connector" defined with it's hierarchy as

Oracle Connector --> JDBC Connector --> Connector

where Teiid defines properties at each level, but when the def file these properties are flattened and all properties are written under component type "Oracle Connector".

Looking at the issue, "ComponentType" fragment of the XML is optional, if the connector type is already in the "configuration.xml". However, designer still need to write the ComponentType information for custom connector types as that information will not be in the configuration.xml file.

To determine, if a connector type is already in the "configuration.xml", the designer can check a property called "standard", if the value is "true" it can safely ignore adding the component type to the .def file.

Teiid will supply the configuration.xml file with "standard" property set on all the built in types.