May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1289) After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1289?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1289: ----------------------------------- Fix Version/s: 8.2 > After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1289 > URL: https://issues.jboss.org/browse/TEIIDDES-1289 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2 > > > After importing the metadata using the modeshape jdbc driver, I created the ModeShape.vdb and tried to deploy. It wouldn't deploy because the connection information was not in the ModeShape.xmi model. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1289) After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1289?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1289: ----------------------------------- Assignee: Mark Drilling (was: Barry LaFond) > After importing metadata using the ModeShape jdbc driver, the connection information was not propagated from the connection profile > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1289 > URL: https://issues.jboss.org/browse/TEIIDDES-1289 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.2 > > > After importing the metadata using the modeshape jdbc driver, I created the ModeShape.vdb and tried to deploy. It wouldn't deploy because the connection information was not in the ModeShape.xmi model. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1413) An Error occurred fetching the Query Plan.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1413?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1413. ------------------------------------ Assignee: Barry LaFond Resolution: Cannot Reproduce Bug Designer & Teiid have moved to 8.x versions. Last comment by Teiid indicates server side improvements. Not enough info to reproduce. > An Error occurred fetching the Query Plan. > ------------------------------------------ > > Key: TEIIDDES-1413 > URL: https://issues.jboss.org/browse/TEIIDDES-1413 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.7 > Environment: Teiid Designer 7.7 > Teiid Server 7.5 > Jboss-5.1.0.GA > JDK 1.6.0_22 > Reporter: thanh nguyen > Assignee: Barry LaFond > > Step by step: > Step 1: Right click Procedure > Choose Modeling > Choose Preview Data > Step 2: Display error below: > org.teiid.jdbc.TeiidSQLException: ResultSet cursor is after the last row. > at org.teiid.jdbc.ResultSetImpl.getObject(ResultSetImpl.java:220) > at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:837) > at org.teiid.jdbc.ResultSetImpl.getString(ResultSetImpl.java:842) > at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable.getExecutionPlan(TeiidAdHocScriptRunnable.java:326) > at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable.handleShowExecutionPlan(TeiidAdHocScriptRunnable.java:243) > at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable.run(TeiidAdHocScriptRunnable.java:223) > at org.eclipse.datatools.sqltools.editor.core.result.ResultSupportRunnable.run(ResultSupportRunnable.java:346) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.internalRun(PreviewDataWorker.java:427) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.run(PreviewDataWorker.java:250) > at org.teiid.designer.runtime.ui.preview.PreviewTableDataContextAction.run(PreviewTableDataContextAction.java:98) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) > at org.eclipse.equinox.launcher.Main.run(Main.java:1410) > at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1341) Input of Sybase Procedures sets all parameters as UNKNOWN and Designer gives only warnings not errors on the direction not being set

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1341?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1341: ----------------------------------- Assignee: Mark Drilling > Input of Sybase Procedures sets all parameters as UNKNOWN and Designer gives only warnings not errors on the direction not being set > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1341 > URL: https://issues.jboss.org/browse/TEIIDDES-1341 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.2 > > > Sybase import sets all parameters to a direction of UNKNOWN, validation only shows this as a warning, it should be an error -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1341) Input of Sybase Procedures sets all parameters as UNKNOWN and Designer gives only warnings not errors on the direction not being set

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1341?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1341: ----------------------------------- Fix Version/s: 8.2 > Input of Sybase Procedures sets all parameters as UNKNOWN and Designer gives only warnings not errors on the direction not being set > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1341 > URL: https://issues.jboss.org/browse/TEIIDDES-1341 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Fix For: 8.2 > > > Sybase import sets all parameters to a direction of UNKNOWN, validation only shows this as a warning, it should be an error -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1484) File Source importer reverses view/table name typing on Windows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1484?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1484: ----------------------------------- Fix Version/s: 8.2 > File Source importer reverses view/table name typing on Windows > --------------------------------------------------------------- > > Key: TEIIDDES-1484 > URL: https://issues.jboss.org/browse/TEIIDDES-1484 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Environment: JBDS 5.0.0 on Windows > Reporter: Hisanobu Okuda > Assignee: Johnathon Lee > Fix For: 8.2 > > > In JBoss Developer Studio 5.0, I noticed an Issue in entering new view table name in the File source Import wizard. When we try to type each character to name the new view table , cursor goes to beginning of the field. It might be relevant with [1] and [2]. > [1] [https://issues.jboss.org/browse/TEIIDDES-1421] > [2] [https://issues.jboss.org/browse/JBIDE-12205] -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1484) File Source importer reverses view/table name typing on Windows

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1484?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1484: ----------------------------------- Assignee: Dan Florian (was: Johnathon Lee) > File Source importer reverses view/table name typing on Windows > --------------------------------------------------------------- > > Key: TEIIDDES-1484 > URL: https://issues.jboss.org/browse/TEIIDDES-1484 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Environment: JBDS 5.0.0 on Windows > Reporter: Hisanobu Okuda > Assignee: Dan Florian > Fix For: 8.2 > > > In JBoss Developer Studio 5.0, I noticed an Issue in entering new view table name in the File source Import wizard. When we try to type each character to name the new view table , cursor goes to beginning of the field. It might be relevant with [1] and [2]. > [1] [https://issues.jboss.org/browse/TEIIDDES-1421] > [2] [https://issues.jboss.org/browse/JBIDE-12205] -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1440) Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1440?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1440: ----------------------------------- Fix Version/s: 8.2 > Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1440 > URL: https://issues.jboss.org/browse/TEIIDDES-1440 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 7.6 > Environment: JBDS 5 Beta 3 on Fedora 16 > Reporter: Joel Tosi > Fix For: 8.2 > > > I connect to a remote Teiid Server (EDS) all is fine. I deploy, no issue. I then go to stop the server (right click on server, stop) and the log updates showing the server is shutting down, but never completes. In eclipse, it appears that the server is still running though I can verify that the process is no longer up. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1440) Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1440?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1440: ----------------------------------- Assignee: Paul Richardson > Stopping remote Teiid server stays in 'Stopping status' even after server is down. Then can't restart > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1440 > URL: https://issues.jboss.org/browse/TEIIDDES-1440 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 7.6 > Environment: JBDS 5 Beta 3 on Fedora 16 > Reporter: Joel Tosi > Assignee: Paul Richardson > Fix For: 8.2 > > > I connect to a remote Teiid Server (EDS) all is fine. I deploy, no issue. I then go to stop the server (right click on server, stop) and the log updates showing the server is shutting down, but never completes. In eclipse, it appears that the server is still running though I can verify that the process is no longer up. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1731) When importing a file and creating the File connector profile on windows, unable to specify linux file location

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1731?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1731: ----------------------------------- Fix Version/s: 8.2 > When importing a file and creating the File connector profile on windows, unable to specify linux file location > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1731 > URL: https://issues.jboss.org/browse/TEIIDDES-1731 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 7.8 > Environment: Windows desktop deploying to EDS running on RHEL > Reporter: Van Halbert > Fix For: 8.2 > > > When importing a file, need to define the connection profile. Unable to specify a linux file path to the file. Have to use windows format, and then goto the server and change the location post datasource deployment. Can the connection profile be changed to accept a linux file format on a windows desktop? -- 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

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2013