[JBoss JIRA] (TEIIDDES-2950) Existing data source is not overridden
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2950?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2950.
----------------------------------
> Existing data source is not overridden
> --------------------------------------
>
> Key: TEIIDDES-2950
> URL: https://issues.jboss.org/browse/TEIIDDES-2950
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: screenshot.png
>
>
> When a user creates datasource with a name which already exists, a user can click OK but this datasource won't be overridden. In the wizard is warning (screenshot) that "A Data Source with the name SQL_Server_2008_Books_DS already exists." but a user can click OK. A user can think that datasource was overridden.
> This is confusing so I think that designer should show some warning that datasource will not be overridden or the OK button should be disabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2950) Existing data source is not overridden
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2950?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2950:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.3 (was: )
> Existing data source is not overridden
> --------------------------------------
>
> Key: TEIIDDES-2950
> URL: https://issues.jboss.org/browse/TEIIDDES-2950
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: screenshot.png
>
>
> When a user creates datasource with a name which already exists, a user can click OK but this datasource won't be overridden. In the wizard is warning (screenshot) that "A Data Source with the name SQL_Server_2008_Books_DS already exists." but a user can click OK. A user can think that datasource was overridden.
> This is confusing so I think that designer should show some warning that datasource will not be overridden or the OK button should be disabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2961.
----------------------------------
> Using JDG CP, unable to create data source without entering AliasCacheName property
> -----------------------------------------------------------------------------------
>
> Key: TEIIDDES-2961
> URL: https://issues.jboss.org/browse/TEIIDDES-2961
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
> Attachments: JDGConnectionInfoProvider.patch, JDGProfileDetailsWizardPage.patch
>
>
> Created a JDG connection profile to connect to an existing JDG cache. When I select the create DataSource option, it present a dialog that indicated the AliashCacheName cannot be null. The AliasCacheName and StagingCacheName should be empty if not using materialization.
> StackTrace:
> java.lang.IllegalArgumentException: No value for the connection property 'AliasCacheName'
> at org.teiid.core.designer.util.CoreArgCheck.isNotZeroLength(CoreArgCheck.java:117)
> at org.teiid.core.designer.util.CoreArgCheck.isNotEmpty(CoreArgCheck.java:249)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:662)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:185)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2983) Unable to create data source using "Use Connection Profile" option
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2983?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-2983:
----------------------------------
Description: When trying create the data source get the attached error when using the option to "Use Connection Profile". This doesn't occur when using model connection info. (was: When trying create the data source, now get the attached error. This only started happening in the latest build "70")
> Unable to create data source using "Use Connection Profile" option
> ------------------------------------------------------------------
>
> Key: TEIIDDES-2983
> URL: https://issues.jboss.org/browse/TEIIDDES-2983
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Priority: Blocker
> Attachments: createdatasourceerror.png
>
>
> When trying create the data source get the attached error when using the option to "Use Connection Profile". This doesn't occur when using model connection info.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months