[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2961:
-----------------------------------
Attachment: JDGProfileDetailsWizardPage.patch
JDGConnectionInfoProvider.patch
> 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
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2961:
---------------------------------------
Steps:
- create connection profile
- create model
- set CP to model
- create data source gets the error
> 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
>
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2961:
---------------------------------------
The issue is because I deselected Materialization, but the logic still thinks its needed.
> 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
>
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2953) Static VDB with JDG materialization has a warning after deploy
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2953?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2953:
----------------------------------------
[~shawkins] is there any way to determine from the warning message what metadata might be different/wrong or incomplete?
> Static VDB with JDG materialization has a warning after deploy
> --------------------------------------------------------------
>
> Key: TEIIDDES-2953
> URL: https://issues.jboss.org/browse/TEIIDDES-2953
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.3
>
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. When I want to deploy static VDB, server shows me error that:
> {code:java}
> 15:47:10,347 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue9) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE array_get(strings, index)" with the SQL statement "execute BookCacheSource.native('truncate cache')" due to: TEIID30357 BookCacheSource.native does not exist.
> {code}
> But when I deploy dynamic VDB, which is generated from that staticVDB, server doesn't shows any errors and materialization works fine.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2953) Static VDB with JDG materialization has a warning after deploy
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2953?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2953:
-----------------------------------
Fix Version/s: 10.0.3
(was: 10.0.2)
> Static VDB with JDG materialization has a warning after deploy
> --------------------------------------------------------------
>
> Key: TEIIDDES-2953
> URL: https://issues.jboss.org/browse/TEIIDDES-2953
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.3
>
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. When I want to deploy static VDB, server shows me error that:
> {code:java}
> 15:47:10,347 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue9) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE array_get(strings, index)" with the SQL statement "execute BookCacheSource.native('truncate cache')" due to: TEIID30357 BookCacheSource.native does not exist.
> {code}
> But when I deploy dynamic VDB, which is generated from that staticVDB, server doesn't shows any errors and materialization works fine.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2961:
-------------------------------------
Summary: 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
Priority: Blocker
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.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2961) Using JDG CP, unable to create data source without entering AliasCacheName property
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2961?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-2961:
-------------------------------------
Assignee: Barry LaFond
> 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
>
> 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.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2956) Designer has generated the wrong jar in the JDG module
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2956?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2956:
----------------------------------------
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/86de0386730283c66...
[~mkralik] I hope this change fixes the Windows issue. Didn't have a windows box to run Designer in so won't resolve until you can re-test with next milestone
> Designer has generated the wrong jar in the JDG module
> -------------------------------------------------------
>
> Key: TEIIDDES-2956
> URL: https://issues.jboss.org/browse/TEIIDDES-2956
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Windows 10 1607
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 10.0.2
>
> Attachments: Book_fedora.jar, Book_windows10.jar, completeJDGproject3.zip, express-zip-contents-on-windows.png, jarInFedora.png, jarInWindows.png
>
>
> I want to deploy dynamic vdb with JDG materialization on the server and server shows me error that:
> {code:java}
> IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: java.lang.ClassNotFoundException: org.teiid.jdg.pojo.Book from [Module "org.teiid.jdg.pojo:main" from local module loader @16f65612 (finder: local module finder @311d617d (roots: C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\dv,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\base\.overlays\layer-base-jboss-eap-6.4.9.CP,C:\Users\jboss\Downloads\testJDG\EAP-6.4.0\modules\system\layers\base))]
> {code}
> I noticed that something is wrong with generated jar file in the windows because when I use jar file which I generated in the fedora, materialization works fine. I uploaded both jar files.
> The strange thing is that when I open .jar (which was generated in the windows ) via 7-file in the windows, file contains folders to Book.class (org/teiid/jdg/pojo) (jarInWindows.png) but when I open this same .jar in the fedora, file contains .class which have name org\teiid\jdg\pojo/Book.class (jarInFedora.png). Maybe this is the problem.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2908) Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2908?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2908.
------------------------------------
Resolution: Done
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/4b060d6318e317601...
> Errors in Error Log when deploying/undeploying a fuse project into Fuse on EAP
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-2908
> URL: https://issues.jboss.org/browse/TEIIDDES-2908
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.1
> Environment: JBDS 9.1.0.GA + TD 10.0.1.Final-v20160713-1749-B16
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Fix For: 10.0.2
>
> Attachments: errorLog.txt
>
>
> During deploying/undeploying a fuse project into Fuse on EAP 6.3.0.CR2 I saw the following error in Error Log
> {code}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:77)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getJdbcPort(JBoss7ServerUtil.java:237)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:114)
> at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:560)
> at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:712)
> at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:477)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:433)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil.saveServer(WizardTaskUtil.java:112)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil$2.performFinish(WizardTaskUtil.java:51)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.executeTask(TaskWizard.java:268)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard$2.run(TaskWizard.java:215)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2225)
> at org.eclipse.wst.server.ui.internal.wizard.page.WorkspaceRunnableAdapter.run(WorkspaceRunnableAdapter.java:35)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [
> {"socket-binding-group" => "standard-sockets"},
> {"socket-binding" => "teiid-jdbc"}
> ]. Failure was "JBAS014807: Management resource '[
> (\"socket-binding-group\" => \"standard-sockets\"),
> (\"socket-binding\" => \"teiid-jdbc\")
> ]' not found".
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months
[JBoss JIRA] (TEIIDDES-2881) Sizing issue in Teiid designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2881?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2881:
-----------------------------------
Fix Version/s: 10.0.3
(was: 10.0.2)
> Sizing issue in Teiid designer
> ------------------------------
>
> Key: TEIIDDES-2881
> URL: https://issues.jboss.org/browse/TEIIDDES-2881
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 10.0.1
> Reporter: Harshul Madan
> Assignee: Barry LaFond
> Fix For: 10.0.3
>
> Attachments: Screen Shot 2016-07-22 at 9.01.00 AM.png, Screen Shot 2016-07-22 at 9.01.16 AM-1.png
>
>
> When we click on “Reconciler” icon in Transformation editor. The components in the window which opens is not programmed to support different screen size (i.e. doesn’t scale adequately).
> Details:
> MacBook Pro (Retina, 13.3-inch (2560 x 1600))
> Teiid Designer 9.0
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 6 months