[
https://jira.jboss.org/jira/browse/TEIIDDES-224?page=com.atlassian.jira.p...
]
Ramesh Reddy commented on TEIIDDES-224:
---------------------------------------
Talking to Steve, he was questioning the fact that the Component Types being available at
all in the ".def" file, whether it is a customer connector or not. Teiid does
not support the "vdb" scoped "Connector Type", so why are we including
them in the VDB.
I could not think of any reason to not to agree on this, there is no good reason. For the
custom connector type, user needs to add the extension jar file any way, so if adds the
type information too then we can completely eliminate this step. If they used the CAF then
it is not an issue either.
Anybody can think of reason this is needed?
The ConfigurationInfo.def file has verbose settings for the
ComponentTypes
--------------------------------------------------------------------------
Key: TEIIDDES-224
URL:
https://jira.jboss.org/jira/browse/TEIIDDES-224
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Affects Versions: 6.1.0
Reporter: Ramesh Reddy
Fix For: 6.2.0
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira