November 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1594) Changing Teiid server display name does not update Default Teiid Server panel name

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1594?page=com.atlassian.jira.plu... ] Ted Jones reopened TEIIDDES-1594: --------------------------------- Seeing this issue in 8.3, so re-opening. > Changing Teiid server display name does not update Default Teiid Server panel name > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1594 > URL: https://issues.jboss.org/browse/TEIIDDES-1594 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > * Installed new kit > * Created default server but did not enter Teiid Server display name > * Started server and default mm://localhost:9999 was displayed > * Changed teiid server name to Teiid 8.2 > * Default server name panel did not show updated 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1958) Hang generating war

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1958?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1958: ------------------------------------- Attachment: error.png After quite a long while, designer did come back with the following dialog. > Hang generating war > ------------------- > > Key: TEIIDDES-1958 > URL: https://issues.jboss.org/browse/TEIIDDES-1958 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.3 > Environment: Fedora 17, KDE, runing the DV ER4 tooling/server > Reporter: Steven Hawkins > Attachments: error.png, threaddump.txt > > > Working through the web test script to the point where generating a war was called for. Eclipse shows a processing dialog, but goes all grey and unresponsive. See the attached thread dump. > Not this is in the same workspace as TEIIDDES-1957 so something else could be lingering. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1958) Hang generating war

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1958?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1958: ------------------------------------------ The error log entry is: java.lang.RuntimeException: org.xml.sax.SAXParseExceptionpublicId: http://www.metamatrix.com/metamodels/SimpleDatatypes-instance; systemId: http://www.metamatrix.com/metamodels/SimpleDatatypes-instance; lineNumber: 8; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>". at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:719) at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) at org.eclipse.jface.window.Window.open(Window.java:802) at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171) at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) 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:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) 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:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > Hang generating war > ------------------- > > Key: TEIIDDES-1958 > URL: https://issues.jboss.org/browse/TEIIDDES-1958 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.3 > Environment: Fedora 17, KDE, runing the DV ER4 tooling/server > Reporter: Steven Hawkins > Attachments: error.png, threaddump.txt > > > Working through the web test script to the point where generating a war was called for. Eclipse shows a processing dialog, but goes all grey and unresponsive. See the attached thread dump. > Not this is in the same workspace as TEIIDDES-1957 so something else could be lingering. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1952) Create an ODA Flat File connection profile "next" button does become active

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1952?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1952: ---------------------------------------- no > Create an ODA Flat File connection profile "next" button does become active > --------------------------------------------------------------------------- > > Key: TEIIDDES-1952 > URL: https://issues.jboss.org/browse/TEIIDDES-1952 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Environment: Fedoa 18, JDK 1.6 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.3 > > > Create an ODA Flat File connection profile - the Finish or Next button are > inactive after the selection of the folder where the file is located, when the "Validate Home Folder" is checked (default checked). Test Connection has no effect, when you uncheck "validate home folder" then the buttons light up > Looks like the the validation is not being done auto-matically nor when the Test Connection is clicked. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1960) Changing connection profile jar then reset CP on Model does not update the jar

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1960: --------------------------------------- Summary: Changing connection profile jar then reset CP on Model does not update the jar Key: TEIIDDES-1960 URL: https://issues.jboss.org/browse/TEIIDDES-1960 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.3 Reporter: Mark Drilling Fix For: 8.3 Changed a CP driver's jar, then reset the CP on source model. When I view connection info on the model, I still see the 'old' jar. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1837) RemoteSystemsTempFiles project is showing up in new project wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1837?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1837: ----------------------------------- Fix Version/s: 8.4 (was: 8.3) Assignee: (was: Barry LaFond) > RemoteSystemsTempFiles project is showing up in new project wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1837 > URL: https://issues.jboss.org/browse/TEIIDDES-1837 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Mark Drilling > Fix For: 8.4 > > Attachments: RemoteSystemsTempFiles.png > > > In the New Model Project Wizard, enter the name of your new project. Click Next. On the second page of the Wizard, a 'RemoteSystemsTempFiles' project is shown. I think the intent is for that project to be hidden. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1837) RemoteSystemsTempFiles project is showing up in new project wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1837?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1837: ---------------------------------------- The second page is inherited from the BasicNewProjectResourceWizard that our wizard extends. So would need to do more work to filter the offending project from the second page > RemoteSystemsTempFiles project is showing up in new project wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1837 > URL: https://issues.jboss.org/browse/TEIIDDES-1837 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Mark Drilling > Fix For: 8.4 > > Attachments: RemoteSystemsTempFiles.png > > > In the New Model Project Wizard, enter the name of your new project. Click Next. On the second page of the Wizard, a 'RemoteSystemsTempFiles' project is shown. I think the intent is for that project to be hidden. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1935) Cancelling wizard for Set the Default JBoss/Teiid Instance Action still sets the default.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1935?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1935. ------------------------------------ Resolution: Done Issue is fixed. > Cancelling wizard for Set the Default JBoss/Teiid Instance Action still sets the default. > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1935 > URL: https://issues.jboss.org/browse/TEIIDDES-1935 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: DefaultInstanceChanged.png > > > 1) Create a single JBoss server with Teiid instance and insure it's set as the default instance > 2) Select *Teiid* action set > 3) d-click *Set the Default JBoss / Teiid Instance* action > 4) cancel dialog by clicking *No* > 5) Dialog still appears stating: *The default teiid instance has been changed to mm://localhost:9999* (See attached image) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1952) Create an ODA Flat File connection profile "next" button does become active

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1952?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1952: ---------------------------------------- I cannot reproduce this with my Ubuntu/Linux either in the DV6/JBDS7.1CR1/Designer8.3CR1 tooling. Also tried in debug and it appears the wizard is properly listening for text change and the folder location change events and executing validation and updating page status. Anything else in your set-up installation that may be different? > Create an ODA Flat File connection profile "next" button does become active > --------------------------------------------------------------------------- > > Key: TEIIDDES-1952 > URL: https://issues.jboss.org/browse/TEIIDDES-1952 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Environment: Fedoa 18, JDK 1.6 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.3 > > > Create an ODA Flat File connection profile - the Finish or Next button are > inactive after the selection of the folder where the file is located, when the "Validate Home Folder" is checked (default checked). Test Connection has no effect, when you uncheck "validate home folder" then the buttons light up > Looks like the the validation is not being done auto-matically nor when the Test Connection is clicked. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1959) JDBC Credential Changes are Reset After Save

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1959: ----------------------------------- Summary: JDBC Credential Changes are Reset After Save Key: TEIIDDES-1959 URL: https://issues.jboss.org/browse/TEIIDDES-1959 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 8.3 Reporter: Ted Jones After changing the JDBC credentials in the Teiid Instance Properties editor and clicking save, the credentials are reset to the default "user". -- 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, 5 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 November 2013