[ https://jira.jboss.org/jira/browse/TEIIDDES-136?page=com.atlassian.jira.p... ] Ramesh Reddy commented on TEIIDDES-136: --------------------------------------- In the ConfigurationInfo.def file, when the designer writes the "ComponentType" for the Connector Type, it writes more information than the original contents from the "configuration.xml", like it has "supports*" properties. These properties are not needed, we should avoid writing those. Fundamentally, we need to decide to add any component-type information either in the configuration.xml or in the VDB, not in both, especially when they contradict each other with different information in each. Also, since there is hierarchy in xml MySQL Connector Type <--- JDBC Connector <-- Connector we only write "MySQL Connector Type" with gleaned information from other two, which is wrong, in the same vein writing all of in single XML node or separate XML nodes, does not see correct. We need to really think about these properties coming from connector itself, not from additional XML file. In the meantime some how embedded is skipping the decryption of the password. -- 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

[ https://jira.jboss.org/jira/browse/TEIIDDES-136?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-136: ---------------------------------- Fix Version/s: Future (was: 6.0.0) Description: Because of changes in Connector API & connector type property changes, the VDB's ConfigurationInfo.def file is containing more info than it needs. We need to filter the "default" properties because they are supplied by default on the server and in teiid embedded. --------- Original Description --------------- I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. Ramesh will fill in the technical details. This prevents using the VDB inside Teiid Embedded. ---------------------------------------------------------- was: I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. Ramesh will fill in the technical details. This prevents using the VDB inside Teiid Embedded. Assignee: (was: Dan Florian) -- 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

[ https://jira.jboss.org/jira/browse/TEIIDDES-193?page=com.atlassian.jira.p... ] Steven Hawkins updated TEIIDDES-193: ------------------------------------ Assignee: Dan Florian (was: Steven Hawkins) After further investigation, the most appropriate fix is on the designer side. We lack the metadata at write time to handle this easily. -- 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