March 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-903) NPE when connecting to SalesForce through the connection profile.

by John Doyle (JIRA)

NPE when connecting to SalesForce through the connection profile. ----------------------------------------------------------------- Key: TEIIDDES-903 URL: https://issues.jboss.org/browse/TEIIDDES-903 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.3 Reporter: John Doyle The SalesForce connection profile cannot connect with valid credentials. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-768) Criteria Builder may insert crieria inside object names if user not careful

by Paul Nittel (JIRA)

Criteria Builder may insert crieria inside object names if user not careful --------------------------------------------------------------------------- Key: TEIIDDES-768 URL: https://issues.jboss.org/browse/TEIIDDES-768 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.1.1 Environment: JBDS 4.0 Beta2 Reporter: Paul Nittel I start with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PARTS; END At this point the Criteria Builder (and Expression Builder) button is disabled. So I click in the SELECT clause to enable the button. Let's say I click between the P and the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with: CREATE VIRTUAL PROCEDURE BEGIN SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR = PartsView.getPartsByColor.colorInRTS; END Regardless of where in the SELECT I click, the WHERE clause should be inserted in a syntactically correct location. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-914) Unable to deploy war generated through Jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS

by Hilal Mushtaque (JIRA)

Unable to deploy war generated through Jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS ----------------------------------------------------------------------------------------------- Key: TEIIDDES-914 URL: https://issues.jboss.org/browse/TEIIDDES-914 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Reporter: Hilal Mushtaque Hi, I am unable to deploy the Web-Service war generated through jbossws-CXF using teiid designer 7.1.0 in Jboss 5.1.0 AS, I am getting below given error on the JBOSS Console DEPLOYMENTS IN ERROR: Deployment "vfszip:/E:/jboss-5.1.0.GA/jboss-5.1.0.GA/server/default/deploy/webService.war/" is in error due to the following reason(s): java.net.ConnectException: Connection refused: connect at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) :faultCode=PARSER_ERROR: Problem parsing 'http://www.metamatrix.com/metamodels/SimpleDatatypes-instance'.: java.net.ConnectException: Connection refused: connect Please suggest ASAP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
20
0 / 0

[JBoss JIRA] Created: (TEIIDDES-710) Add Ability to Create Translator Overrides in Designer

by Ted Jones (JIRA)

Add Ability to Create Translator Overrides in Designer ------------------------------------------------------- Key: TEIIDDES-710 URL: https://jira.jboss.org/browse/TEIIDDES-710 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.1 Reporter: Ted Jones Assignee: Ted Jones Need the ability to ad translator overrides for a VDB. Currently overrides have to be manually added to the vdb.xml. After talking with Barry, the best place for such and editor would be from the Translator field of the models table from within the VDB editor. There is a context menu that allows you to change the translator from that field. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-917) Changes To A VDB Editor's Translator Override Property Does Not Mark The VDB As Dirty

by Dan Florian (JIRA)

Changes To A VDB Editor's Translator Override Property Does Not Mark The VDB As Dirty ------------------------------------------------------------------------------------- Key: TEIIDDES-917 URL: https://issues.jboss.org/browse/TEIIDDES-917 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.3 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.4 After changing a VDB's translator override property, the VDB is not marked as dirty and should be. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-916) Create A Reusable Implementation Of EditingSupport Based On core.designer.PropertyDefinition

by Dan Florian (JIRA)

Create A Reusable Implementation Of EditingSupport Based On core.designer.PropertyDefinition -------------------------------------------------------------------------------------------- Key: TEIIDDES-916 URL: https://issues.jboss.org/browse/TEIIDDES-916 Project: Teiid Designer Issue Type: Task Components: Editors Affects Versions: 7.3 Reporter: Dan Florian Assignee: Dan Florian Priority: Critical Fix For: 7.4 This class will be used by both the VDB Editor and the new model extension framework that Barry is writing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-913) Need a non-i18n version of PluginUtilImpl

by Barry LaFond (JIRA)

Need a non-i18n version of PluginUtilImpl ----------------------------------------- Key: TEIIDDES-913 URL: https://issues.jboss.org/browse/TEIIDDES-913 Project: Teiid Designer Issue Type: Component Upgrade Components: Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.4 In order to NOT use the current Designer's i18n framework and replace with Eclipse's NLS framework, we need a non-i18n version of the PluginUtilImpl that does NOT do i18n string management. Create a LoggingUtil class that implements all PluginUtil methods but throws UnsupportedOperation() exceptions for ALL getString() methods AND only requires a PLUGIN ID in it's constructor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-912) Refactor PropertyDefinition From designer.core to core.designer For Better Reuse

by Dan Florian (JIRA)

Refactor PropertyDefinition From designer.core to core.designer For Better Reuse -------------------------------------------------------------------------------- Key: TEIIDDES-912 URL: https://issues.jboss.org/browse/TEIIDDES-912 Project: Teiid Designer Issue Type: Task Affects Versions: 7.3 Reporter: Dan Florian Assignee: Dan Florian Priority: Critical Fix For: 7.4 Moving PropertyDefinition to a non-Designer packaged plugin makes this class available to plugins that designer.core is dependent on. This refactoring is required to be done in order to resolve TEIIDDES-905. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-911) VdbSourceConnectionHandler Is Referencing Some Incorrect i18n Keys

by Dan Florian (JIRA)

VdbSourceConnectionHandler Is Referencing Some Incorrect i18n Keys ------------------------------------------------------------------ Key: TEIIDDES-911 URL: https://issues.jboss.org/browse/TEIIDDES-911 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.3 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.4 The "invalidPropertyEditornewValue" does not exist in the properties file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-910) Inappropriate cross join warnings are given for nested table functions

by Steven Hawkins (JIRA)

Inappropriate cross join warnings are given for nested table functions ---------------------------------------------------------------------- Key: TEIIDDES-910 URL: https://issues.jboss.org/browse/TEIIDDES-910 Project: Teiid Designer Issue Type: Quality Risk Components: Modeling Affects Versions: 7.1 Reporter: Steven Hawkins Priority: Minor The use of a nested table function reference such as TABLE(...), or any of the XMLTABLE, TEXTTABLE, etc. functions in the from clause will get warnings about possible joins. However they typically are joined by sideways correlation, not through a join/where condition. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2011