July 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1753) Allow Creation of REST based Procedures in Designer

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1753?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1753: -------------------------------- https://github.com/Teiid-Designer/teiid-designer/pull/209 > Allow Creation of REST based Procedures in Designer > --------------------------------------------------- > > Key: TEIIDDES-1753 > URL: https://issues.jboss.org/browse/TEIIDDES-1753 > Project: Teiid Designer > Issue Type: Enhancement > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > Need to allow for creation of REST based procedures as described in https://docs.jboss.org/author/display/teiid82final/REST+Service+Through+VDB. > The only other option is to generate the war in Designer using the REST war generator. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1790) MED Editor metaclass selection dialog does not enable OK button

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1790?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1790. ------------------------------------ Resolution: Done fixed > MED Editor metaclass selection dialog does not enable OK button > ----------------------------------------------------------------- > > Key: TEIIDDES-1790 > URL: https://issues.jboss.org/browse/TEIIDDES-1790 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > MED Editor metaclass selection dialog does not enable OK button and has error icon for "There were no validation errors" state. > Need to enable and remove error icon -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1790) MED Editor metaclass selection dialog does not enable OK button

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1790: -------------------------------------- Summary: MED Editor metaclass selection dialog does not enable OK button Key: TEIIDDES-1790 URL: https://issues.jboss.org/browse/TEIIDDES-1790 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2 MED Editor metaclass selection dialog does not enable OK button and has error icon for "There were no validation errors" state. Need to enable and remove error icon -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1789) Creating new model project does not result in project preview vdb being created. Results in failed preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1789?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1789. ------------------------------------ Resolution: Done Added check to catch the project's resource change event when NATURE_ID is set, then handling as modelProjectOpened() to create/replace the project vdb > Creating new model project does not result in project preview vdb being created. Results in failed preview > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1789 > URL: https://issues.jboss.org/browse/TEIIDDES-1789 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > Project preview vdb is not getting created on New Project actions. it's only created via Open Project resource change event. > Actually the New PRoject action results in open project event, but the Modeler Nature ID is set afterwards and not getting processed -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1789) Creating new model project does not result in project preview vdb being created. Results in failed preview

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1789: -------------------------------------- Summary: Creating new model project does not result in project preview vdb being created. Results in failed preview Key: TEIIDDES-1789 URL: https://issues.jboss.org/browse/TEIIDDES-1789 Project: Teiid Designer Issue Type: Bug Components: Data Preview, VDB & Execution Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2 Project preview vdb is not getting created on New Project actions. it's only created via Open Project resource change event. Actually the New PRoject action results in open project event, but the Modeler Nature ID is set afterwards and not getting processed -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1788) Inclusion of foundation.security plugin in designer feature conflicts with JBDS 7 CR1

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1788?page=com.atlassian.jira.plu... ] Paul Richardson updated TEIIDDES-1788: -------------------------------------- Description: The foundation.security.linux fragment is included in the designer runtime feature. This can conflict with different versions of the plugin installed in versions of JBDS 7. * -Remove the plugin from the Teiid Designer feature since this was only a temporary measure due to lacking the plugin's feature in JBTIS.- Done. * Once [JBTIS-107|https://issues.jboss.org/browse/JBTIS-107] has been resolved, include the foundation.security feature as a dependency. was: The foundation.security.linux fragment is included in the designer runtime feature. This can conflict with different versions of the plugin installed in versions of JBDS 7. * Remove the plugin from the Teiid Designer feature since this was only a temporary measure due to lacking the plugin's feature in JBTIS. * Once [JBTIS-107|https://issues.jboss.org/browse/JBTIS-107] has been resolved, include the foundation.security feature as a dependency. > Inclusion of foundation.security plugin in designer feature conflicts with JBDS 7 CR1 > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1788 > URL: https://issues.jboss.org/browse/TEIIDDES-1788 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Paul Richardson > Fix For: 8.2 > > > The foundation.security.linux fragment is included in the designer runtime feature. This can conflict with different versions of the plugin installed in versions of JBDS 7. > * -Remove the plugin from the Teiid Designer feature since this was only a temporary measure due to lacking the plugin's feature in JBTIS.- Done. > * Once [JBTIS-107|https://issues.jboss.org/browse/JBTIS-107] has been resolved, include the foundation.security feature as a dependency. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1788) Inclusion of foundation.security plugin in designer feature conflicts with JBDS 7 CR1

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1788: ----------------------------------------- Summary: Inclusion of foundation.security plugin in designer feature conflicts with JBDS 7 CR1 Key: TEIIDDES-1788 URL: https://issues.jboss.org/browse/TEIIDDES-1788 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 8.2 Reporter: Paul Richardson Fix For: 8.2 The foundation.security.linux fragment is included in the designer runtime feature. This can conflict with different versions of the plugin installed in versions of JBDS 7. * Remove the plugin from the Teiid Designer feature since this was only a temporary measure due to lacking the plugin's feature in JBTIS. * Once [JBTIS-107|https://issues.jboss.org/browse/JBTIS-107] has been resolved, include the foundation.security feature as a dependency. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1787) Guides view action and wizard properties not behaving properly

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1787: -------------------------------------- Summary: Guides view action and wizard properties not behaving properly Key: TEIIDDES-1787 URL: https://issues.jboss.org/browse/TEIIDDES-1787 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2 Using the Model JDBC Source actions guide and no model project open in workspace... 1) d-click Define Teiid Model Project 2) d-click Create source model from JDBC source 3) New Project wizard is launched again because project name is not properly being set. 1) Create New Model Project in explorer 2) d-click Create source model from JDBC source 3) New Project wizard is launched again because project name is not properly being set. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1767: ---------------------------------------- Ok, opening an issue with AS folks (prod team) seems to be only resolution to this. I tried what they are mentioning on the "workaround", and that does not work, it also requires a restart. On the Designer/Client side, two workarounds exist 1) Restart the server. Note, you do not need to go to server management window for this, you can execute a admin method "restart" for this. I explicitly provided this for this workaround before. 2)Every time you create a data source have a unique name, do not reuse the same name, even if you are creating just correcting a single property say a password. The long term fix MUST come from AS folks, so there is not much Teiid can do here. Ramesh.. > Cannot redeploy a vdb with webservice datasource > ------------------------------------------------ > > Key: TEIIDDES-1767 > URL: https://issues.jboss.org/browse/TEIIDDES-1767 > Project: Teiid Designer > Issue Type: Bug > Reporter: Paul Richardson > Assignee: Ted Jones > Fix For: 8.2 > > > When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed. > 1. Delete all vdb's data sources, including the WSDL webservice data source; > 2. Deploy the vdb > 3. Observe the following error > {code} > !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314 > !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered > !STACK 0 > org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered > at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195) > at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409) > at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277) > at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412) > at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324) > at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551) > 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) > {code} > Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed. > Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1786) Update query metadata interface for update to teiid 8.5 interface

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1786?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1786: ----------------------------------- Description: Per Steve Hawkins 7/17/2013: https://issues.jboss.org/browse/TEIID-2365 for 8.5 removed the ResolverVisitor.setFindShortName method so that we don't have to rely on static/ThreadLocal logic. Instead this value can be set via the QueryMetadataInterface method findShortName. A simple usage pattern is: QueryMetadataInterface metadata = new BasicQueryMetadataWrapper(metadata){ public boolean useOutputName() { return false; }; }; QueryResolver.resolveCommand(command, metadata); Or this could possibly integrated into your workspace metadata in an appropriate manner (considering thread-safe usage, etc.). was:Parsed objects retain much of the original parse string, which is generally unnecessary on the server side. The use of output names should reduced to unnecessary memory consumption. > Update query metadata interface for update to teiid 8.5 interface > ----------------------------------------------------------------- > > Key: TEIIDDES-1786 > URL: https://issues.jboss.org/browse/TEIIDDES-1786 > Project: Teiid Designer > Issue Type: Task > Reporter: Barry LaFond > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > Per Steve Hawkins 7/17/2013: > https://issues.jboss.org/browse/TEIID-2365 for 8.5 removed the ResolverVisitor.setFindShortName method so that we don't have to rely on static/ThreadLocal logic. Instead this value can be set via the QueryMetadataInterface method findShortName. A simple usage pattern is: > QueryMetadataInterface metadata = new BasicQueryMetadataWrapper(metadata){ > public boolean useOutputName() { > return false; > }; > }; > QueryResolver.resolveCommand(command, metadata); > Or this could possibly integrated into your workspace metadata in an appropriate manner (considering thread-safe usage, etc.). -- 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, 9 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 July 2013