October 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1895) Designer doesn't handle it when the default resource adapter isn't defined in the server

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1895?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1895: --------------------------------------- what will be returned when multiple (for 1 type) is defined in the configuration? Or is the types based on the name's, not the type, returned for display? > Designer doesn't handle it when the default resource adapter isn't defined in the server > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1895 > URL: https://issues.jboss.org/browse/TEIIDDES-1895 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > Description of problem: > I commented out the resource-adapter elements in standalone.xml (so that there was only empty element <resource-adapters></resource-adapters> left). > I run those teiid designer tests: > - basic server management use cases (OK) > - test which uses XML document as a data source - fails [1], whole teiid designer message [2] > Lucie > [1] "There was a problem deploying VDB "RecursiveVDB.vdb" to server "mm://localhost:9999::admin" -- and message "Data Source Type file does not exist on server mm://localhost:9999::admin" > [2] java.lang.Exception: Data Source Type file does not exist on server mm://localhost:9999::admin (JBoss EAP 6.1) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:320) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:556) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1895) Designer doesn't handle it when the default resource adapter isn't defined in the server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1895?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1895: ---------------------------------------- If you remove the them from configuration then they are gone, so getDataSourceTemplateNames() will return null or empty list > Designer doesn't handle it when the default resource adapter isn't defined in the server > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1895 > URL: https://issues.jboss.org/browse/TEIIDDES-1895 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > Description of problem: > I commented out the resource-adapter elements in standalone.xml (so that there was only empty element <resource-adapters></resource-adapters> left). > I run those teiid designer tests: > - basic server management use cases (OK) > - test which uses XML document as a data source - fails [1], whole teiid designer message [2] > Lucie > [1] "There was a problem deploying VDB "RecursiveVDB.vdb" to server "mm://localhost:9999::admin" -- and message "Data Source Type file does not exist on server mm://localhost:9999::admin" > [2] java.lang.Exception: Data Source Type file does not exist on server mm://localhost:9999::admin (JBoss EAP 6.1) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:320) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:556) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1883) DDL/Teiid Connection Importer does not show latest data sources for selection

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1883?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1883: ---------------------------------------- create the data source outside the Designer, then launch the wizard > DDL/Teiid Connection Importer does not show latest data sources for selection > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1883 > URL: https://issues.jboss.org/browse/TEIIDDES-1883 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.3 > > > When using "Teiid Connection >> Source Model" importer the very first screen shows the available data sources in the middle of the page. > The list shown here is stale list, it needs to be updated every time wizard is invoked, to show all the data sources in server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1895) Designer doesn't handle it when the default resource adapter isn't defined in the server

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1895?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1895: ----------------------------------------- On designer side, we load a collection of available 'types' via the adminApi call "getDataSourceTemplateNames()". Checking with teiid guys on whether the 'built in' types should still be included (even though not in standalone.xml), or we need to do something on designer side. > Designer doesn't handle it when the default resource adapter isn't defined in the server > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1895 > URL: https://issues.jboss.org/browse/TEIIDDES-1895 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > Description of problem: > I commented out the resource-adapter elements in standalone.xml (so that there was only empty element <resource-adapters></resource-adapters> left). > I run those teiid designer tests: > - basic server management use cases (OK) > - test which uses XML document as a data source - fails [1], whole teiid designer message [2] > Lucie > [1] "There was a problem deploying VDB "RecursiveVDB.vdb" to server "mm://localhost:9999::admin" -- and message "Data Source Type file does not exist on server mm://localhost:9999::admin" > [2] java.lang.Exception: Data Source Type file does not exist on server mm://localhost:9999::admin (JBoss EAP 6.1) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:320) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:556) > at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107) > at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239) > at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1883) DDL/Teiid Connection Importer does not show latest data sources for selection

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1883?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1883: ------------------------------------------- Hey Ramesh, Can you describe the workflow that produces the stale list, please? Playing with the wizard, I see the following: * I have a data source deployed 'ds04'. * I open the wizard and this data source is listed. * I cancel the wizard and delete the data source. * I open the wizard and ds04 is no longer listed. Since the wizard is modal, I cannot delete the source whilst the wizard is displayed so uncertain how the wizard should respond. > DDL/Teiid Connection Importer does not show latest data sources for selection > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1883 > URL: https://issues.jboss.org/browse/TEIIDDES-1883 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.3 > > > When using "Teiid Connection >> Source Model" importer the very first screen shows the available data sources in the middle of the page. > The list shown here is stale list, it needs to be updated every time wizard is invoked, to show all the data sources in server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1896) Upgrade Modeshape client plugin to 3.6

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1896?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1896. --------------------------------------- Resolution: Done > Upgrade Modeshape client plugin to 3.6 > -------------------------------------- > > Key: TEIIDDES-1896 > URL: https://issues.jboss.org/browse/TEIIDDES-1896 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Paul Richardson > Assignee: Paul Richardson > Priority: Blocker > Fix For: 8.3 > > > Upgrade the modeshape plugin to Modeshape 3.6 bits released on Nexus. This is required pre-release and as soon as the bits are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1900) Parameter map in generated rest war not thread safe

by Steven Hawkins (JIRA)

Steven Hawkins created TEIIDDES-1900: ---------------------------------------- Summary: Parameter map in generated rest war not thread safe Key: TEIIDDES-1900 URL: https://issues.jboss.org/browse/TEIIDDES-1900 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.8 Reporter: Steven Hawkins The parameter map is held as an instance variable which is not thread safe. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1897) Teiid Connection Importer is using the pool-name instead of jndi name

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1897?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1897: ----------------------------------------- I did some debugging - this is actually an issue with the AdminAPI getDataSourceNames() method. It is returning the pool name rather than the jndi name. I never noticed before because I was using same names. > Teiid Connection Importer is using the pool-name instead of jndi name > --------------------------------------------------------------------- > > Key: TEIIDDES-1897 > URL: https://issues.jboss.org/browse/TEIIDDES-1897 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > > When using the "Teiid Connection" importer the data sources are identified with "pool-name" rather than the "jndi" name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1897) Teiid Connection Importer is using the pool-name instead of jndi name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1897?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1897: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1023216|https://bugzilla.redhat.com/show_bug.cgi?id=1023216] from NEW to ASSIGNED > Teiid Connection Importer is using the pool-name instead of jndi name > --------------------------------------------------------------------- > > Key: TEIIDDES-1897 > URL: https://issues.jboss.org/browse/TEIIDDES-1897 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > > When using the "Teiid Connection" importer the data sources are identified with "pool-name" rather than the "jndi" name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1897) Teiid Connection Importer is using the pool-name instead of jndi name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1897?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1897: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1023216 > Teiid Connection Importer is using the pool-name instead of jndi name > --------------------------------------------------------------------- > > Key: TEIIDDES-1897 > URL: https://issues.jboss.org/browse/TEIIDDES-1897 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > > When using the "Teiid Connection" importer the data sources are identified with "pool-name" rather than the "jndi" name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2013