[teiid-issues] [JBoss JIRA] Updated: (TEIID-652) Custom Connectors: Teiid looks in configuration.xml--not ConfigurationInfo.def--for connector information

Wed Jun 10 18:14:56 EDT 2009

     [ https://jira.jboss.org/jira/browse/TEIID-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-652:
---------------------------------

    Workaround Description: To make embedded aware of the custom connector, the component type and all necessary parent component types should be added to the configuration.xml referenced by the deploy.properties.
             Fix Version/s: 6.2.0
                Workaround: [Workaround Exists]

See the workaround.

> 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: Steven Hawkins
>             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