[JBoss JIRA] (TEIIDDES-2527) Changing parameter type in REST Connection Profile wizard causes NPE
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2527?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2527:
-----------------------------------
Fix Version/s: 9.1
9.0.2
8.6.2
> 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
> Assignee: Barry LaFond
> Fix For: 9.1, 9.0.2, 8.6.2
>
>
> 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
[JBoss JIRA] (TEIIDDES-2527) Changing parameter type in REST Connection Profile wizard causes NPE
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2527?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2527:
--------------------------------------
Assignee: Barry LaFond
> 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
> Assignee: Barry LaFond
>
> 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
[JBoss JIRA] (TEIIDDES-2419) Flat file import - models in two project folders
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2419?page=com.atlassian.jira.plu... ]
Andrej Šmigala edited comment on TEIIDDES-2419 at 5/18/15 9:22 AM:
-------------------------------------------------------------------
The check for the same project is done in the following way:
{code:java}! ( viewModelLocation.segment(0).equalsIgnoreCase(sourceModelLocation.segment(0)) ){code}
However, model project names are case sensitive if the underlying filesystem is case sensitive.
Indeed, creating two projects such as p1 and P1, you can still put the source and view model into two different projects.
was (Author: asmigala):
The check for the same project is done in the following way:
{code:java}! ( viewModelLocation.segment(0).equalsIgnoreCase(sourceModelLocation.segment(0)) ){code}
However, model project names are case sensitive.
Indeed, creating two projects such as p1 and P1, you can still put the source and view model into two different projects.
> Flat file import - models in two project folders
> ------------------------------------------------
>
> Key: TEIIDDES-2419
> URL: https://issues.jboss.org/browse/TEIIDDES-2419
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: screen1.png, screen2.png, screen3.png
>
>
> When importing from Flat file, TD allows user to put models (source and view) in different model project folders.
> See screenshots
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2419) Flat file import - models in two project folders
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2419?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2419:
--------------------------------------
The check for the same project is done in the following way:
{code:java}! ( viewModelLocation.segment(0).equalsIgnoreCase(sourceModelLocation.segment(0)) ){code}
However, model project names are case sensitive.
Indeed, creating two projects such as p1 and P1, you can still put the source and view model into two different projects.
> Flat file import - models in two project folders
> ------------------------------------------------
>
> Key: TEIIDDES-2419
> URL: https://issues.jboss.org/browse/TEIIDDES-2419
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
> Attachments: screen1.png, screen2.png, screen3.png
>
>
> When importing from Flat file, TD allows user to put models (source and view) in different model project folders.
> See screenshots
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2422:
--------------------------------------
This is not fully fixed:
When following the steps as described, the schema model is created in the correct folder, however, an extra empty web service model is created in the root of the project (in addition to the one created in web_services folder, which contains the operation from the wsdl).
Additionally, when creating the model by right clicking the web_services folder and selecting New -> Teiid Metadata Model, the import shows the same behaviour as before, i.e. the schema model is created in <project>/web_services/schemas instead of <project>/schemas.
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months