Ramesh Reddy created TEIIDDES-2235: -------------------------------------- Summary: Preview uses Pool Name instead of JNDI name Key: TEIIDDES-2235 URL: https://issues.jboss.org/browse/TEIIDDES-2235 Project: Teiid Designer Issue Type: Bug Security Level: Public (Everyone can see) Components: Data Preview Reporter: Ramesh Reddy Priority: Critical I am using almost latest 8.5-nightly, and latest 8.8 Teiid. I created a file data source in server using CLI {code} /subsystem=resource-adapters/resource-adapter=fileExcel:add(module=org.jboss.teiid.resource-adapter.file) /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS:add(jndi-name="java:/excel-ds", class-name=org.teiid.resource.adapter.file.FileManagedConnectionFactory, enabled=true, use-java-context=true) /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS/config-properties=ParentDirectory:add(value="/home/rareddy/Downloads" ) /subsystem=resource-adapters/resource-adapter=fileExcel:activate {code} here fileExcel = is resource adapter name fileDS = pool-name java:/excel-ds = JNDI name All the communication over the Admin API occurs over "pool-name", however JNDI name is what should be used in the "connection-jndi-name" Now, I used "Teiid Connection Importer" to import from data source created above, used "excel" translator, created a model. It created a "sheet1" table. Now right click preview, I see {code} org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 Names: TEIID30481 Failed to find the Connection Factory with JNDI name fileDS. Please check the name or deploy the Connection Factory with specified name. {code} which is wrong. "Right-Click -> View Connection Profile Dialog" attached. I have been suggesting to use a simple "JNDI" based data source connection profile for dealing with the data sources on server to avoid issues like this, and I see designer is going more towards other side adding dependencies like BIRT etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264)