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

[JBoss JIRA] (TEIIDDES-2444) Import flat file via remote URL problem

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2444?page=com.atlassian.jira.plu... ] Andrej Šmigala reopened TEIIDDES-2444: -------------------------------------- The changed code contains the following line: {code:java} if( info == null && !info.viewModelExists() ) { {code} This would cause NPE in case info is ever null, it should probably have been || instead of &&. However, the null check seems redundant, as info is only set in the constructor and it is checked for null there. > Import flat file via remote URL problem > --------------------------------------- > > Key: TEIIDDES-2444 > URL: https://issues.jboss.org/browse/TEIIDDES-2444 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6.1 > Reporter: Jan Stastny > Assignee: Barry LaFond > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > > When importing flat file via remote URL the import can't be finished. It gets stuck on screen 'Flat File Delimited Columns Parser Settings' where the 'next' button is enabled, but nothing happens after clicking it. > I encountered the issue while performing this test script: https://mojo.redhat.com/docs/DOC-1016720 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2528) REST connection profile dialog unusable at low resolution screens

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2528?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2528: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1222514 > REST connection profile dialog unusable at low resolution screens > ----------------------------------------------------------------- > > Key: TEIIDDES-2528 > URL: https://issues.jboss.org/browse/TEIIDDES-2528 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 9.0.2 Beta1 > Reporter: Andrej Šmigala > Attachments: rest-cp.png > > > The parameters cannot be edited at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2528) REST connection profile dialog unusable at low resolution screens

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2528?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2528: ------------------------------------- Attachment: rest-cp.png > REST connection profile dialog unusable at low resolution screens > ----------------------------------------------------------------- > > Key: TEIIDDES-2528 > URL: https://issues.jboss.org/browse/TEIIDDES-2528 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 9.0.2 Beta1 > Reporter: Andrej Šmigala > Attachments: rest-cp.png > > > The parameters cannot be edited at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2528) REST connection profile dialog unusable at low resolution screens

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2528: ---------------------------------------- Summary: REST connection profile dialog unusable at low resolution screens Key: TEIIDDES-2528 URL: https://issues.jboss.org/browse/TEIIDDES-2528 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 9.0.2 Beta1 Reporter: Andrej Šmigala Attachments: rest-cp.png The parameters cannot be edited at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2527) Changing parameter type in REST Connection Profile wizard causes NPE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2527?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2527: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1222511 > Changing parameter type in REST Connection Profile wizard causes NPE > -------------------------------------------------------------------- > > Key: TEIIDDES-2527 > URL: https://issues.jboss.org/browse/TEIIDDES-2527 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration, Import/Export > Affects Versions: 9.0.2 Beta1 > Reporter: Andrej Šmigala > > The Parameters section of the REST Connection Profile wizard allows the user to freely edit the Type column. However, when entering anything else apart from 'URI' and 'Query', a Problem Occured dialog is shown. The value in the Type column cannot be edited afterwards, nor can the parameter be deleted. > Ideally, the text input should be replaced with a drop-down. > The following is logged: > {noformat} > java.lang.NullPointerException > at org.teiid.designer.datatools.profiles.ws.ParameterPanel$PropertyNameEditingSupport.setValue(ParameterPanel.java:437) > at org.eclipse.jface.viewers.EditingSupport.saveCellEditorValue(EditingSupport.java:113) > at org.eclipse.jface.viewers.ColumnViewerEditor.saveEditorValue(ColumnViewerEditor.java:463) > at org.eclipse.jface.viewers.ColumnViewerEditor.applyEditorValue(ColumnViewerEditor.java:319) > at org.eclipse.jface.viewers.ColumnViewerEditor.handleEditorActivationEvent(ColumnViewerEditor.java:446) > at org.eclipse.jface.viewers.ColumnViewer.triggerEditorActivationEvent(ColumnViewer.java:675) > at org.eclipse.jface.viewers.ColumnViewer.handleMouseDown(ColumnViewer.java:650) > at org.eclipse.jface.viewers.ColumnViewer.access$0(ColumnViewer.java:646) > at org.eclipse.jface.viewers.ColumnViewer$1.mouseDown(ColumnViewer.java:95) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:192) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2527) Changing parameter type in REST Connection Profile wizard causes NPE

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2527: ---------------------------------------- Summary: Changing parameter type in REST Connection Profile wizard causes NPE Key: TEIIDDES-2527 URL: https://issues.jboss.org/browse/TEIIDDES-2527 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration, Import/Export Affects Versions: 9.0.2 Beta1 Reporter: Andrej Šmigala The Parameters section of the REST Connection Profile wizard allows the user to freely edit the Type column. However, when entering anything else apart from 'URI' and 'Query', a Problem Occured dialog is shown. The value in the Type column cannot be edited afterwards, nor can the parameter be deleted. Ideally, the text input should be replaced with a drop-down. The following is logged: {noformat} java.lang.NullPointerException at org.teiid.designer.datatools.profiles.ws.ParameterPanel$PropertyNameEditingSupport.setValue(ParameterPanel.java:437) at org.eclipse.jface.viewers.EditingSupport.saveCellEditorValue(EditingSupport.java:113) at org.eclipse.jface.viewers.ColumnViewerEditor.saveEditorValue(ColumnViewerEditor.java:463) at org.eclipse.jface.viewers.ColumnViewerEditor.applyEditorValue(ColumnViewerEditor.java:319) at org.eclipse.jface.viewers.ColumnViewerEditor.handleEditorActivationEvent(ColumnViewerEditor.java:446) at org.eclipse.jface.viewers.ColumnViewer.triggerEditorActivationEvent(ColumnViewer.java:675) at org.eclipse.jface.viewers.ColumnViewer.handleMouseDown(ColumnViewer.java:650) at org.eclipse.jface.viewers.ColumnViewer.access$0(ColumnViewer.java:646) at org.eclipse.jface.viewers.ColumnViewer$1.mouseDown(ColumnViewer.java:95) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:192) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) at org.eclipse.jface.window.Window.open(Window.java:808) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:606) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2451) Rest connection profile - Add new parameter dialogue problem - Can not select type "URI"

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2451?page=com.atlassian.jira.plu... ] Andrej Šmigala closed TEIIDDES-2451. ------------------------------------ Verified with Teiid Designer 9.0.2 Beta1 > Rest connection profile - Add new parameter dialogue problem - Can not select type "URI" > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-2451 > URL: https://issues.jboss.org/browse/TEIIDDES-2451 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.6.1 > Environment: Windows 7 > Reporter: Matus Makovy > Assignee: Ted Jones > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: out.webm > > > When you are adding parameter to Rest connection profile, you can not change type from Query to URI > See attached video. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2526) Import from SOAP wizard pops up multiple validation result messages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2526?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2526: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1222504 > Import from SOAP wizard pops up multiple validation result messages > ------------------------------------------------------------------- > > Key: TEIIDDES-2526 > URL: https://issues.jboss.org/browse/TEIIDDES-2526 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Web Services Support > Affects Versions: 9.0.2 Beta1 > Reporter: Andrej Šmigala > > Clicking around the SOAP import wizard, the WSDL Validation Results message pops up several times, sometimes showing the wrong result (validation success when the connection profiles is in fact invalid). > Also, when opening the wizard again after closing it, a validation error pops up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2526) Import from SOAP wizard pops up multiple validation result messages

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIIDDES-2526: ---------------------------------------- Summary: Import from SOAP wizard pops up multiple validation result messages Key: TEIIDDES-2526 URL: https://issues.jboss.org/browse/TEIIDDES-2526 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Web Services Support Affects Versions: 9.0.2 Beta1 Reporter: Andrej Šmigala Clicking around the SOAP import wizard, the WSDL Validation Results message pops up several times, sometimes showing the wrong result (validation success when the connection profiles is in fact invalid). Also, when opening the wizard again after closing it, a validation error pops up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Marek Baluch (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Marek Baluch updated TEIIDDES-2436: ----------------------------------- Issue Type: Bug (was: Feature Request) > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.6.2 Beta1, 8.6.2, 9.2, 9.0.3 > > Attachments: import-vdb.png, JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 5 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 May 2015