[
https://jira.jboss.org/jira/browse/TEIID-652?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-652.
--------------------------------
Resolution: Done
Corrected issue such that if the default properties for the connector type are not found
in the configuration.xml, then the default properties from the connector type object
instantiated will be taken. Also, stream lined the loading of VDB during the
initialization of the embedded configuration service similar to that of adding VDB through
admin api, so that there is only one way to load a VDB.
Custom Connectors: Teiid looks in configuration.xml--not
ConfigurationInfo.def--for connector information
---------------------------------------------------------------------------------------------------------
Key: TEIID-652
URL:
https://jira.jboss.org/jira/browse/TEIID-652
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.1.0
Environment: fedora 10, java 1.6.0_10b33, Teiid 6.1.0M4, Designer 6/1/09
Reporter: Paul Nittel
Assignee: Ramesh Reddy
Fix For: 6.2.0
Attachments: configuration.xml, Jahoo.vdb, JahooFromDesigner.vdb
I created the Yahoo UDF project and tested it in the Designer. All OK.
I exported the VDB to Teiid/deploy and copied the connector jars to Teiid/extensions. I
was able to query the two relational sources, but not Yahoo. Ramesh and I found we could
add the ConnectorClass and ConnectorClassPath properties to the yahoo binding section of
ConfigurationInfo.def and it would work. Deleting those and copying the entire Yahoo
ConnectorType sectioninto configuration.xml also worked.
Teiid is looking in the wrong place for the connector type information. (Artifacts are
attached.)
--
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