[JBoss JIRA] (TEIIDDES-2799) Import Geometry types
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2799?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2799:
-----------------------------------
Fix Version/s: 11.3
(was: 11.2)
> Import Geometry types
> ---------------------
>
> Key: TEIIDDES-2799
> URL: https://issues.jboss.org/browse/TEIIDDES-2799
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0.1
> Reporter: Matej Kralik
> Fix For: 11.3
>
> Attachments: screenshot1.png, screenshot2.png
>
>
> In the Maria DB I create tables with contain geometry type.
> Each table contains one of type(POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION, GEOMETRY)).
> When I generated source model from their, only geometry has been set geometry type (screenshot 1). The others have been set object type.
> I generate VDB and execute it. This query
> {code:java}
> SELECT ST_AsText(g) FROM gis_geometry
> {code}
> works only geometry type (screenshot 1). However when I set geometry type manually for all columns in source model, query works for all tables (screenshot 2).
> I think that Teiid Designer will should set geometry type for all this types when it import tables from JDBC source.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2794) Connecting to remote server and refreshing produces an exception
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2794?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2794.
------------------------------------
Assignee: (was: Paul Richardson)
Resolution: Won't Fix
> Connecting to remote server and refreshing produces an exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2794
> URL: https://issues.jboss.org/browse/TEIIDDES-2794
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
> Attachments: Screen Shot 2016-02-25 at 11.31.43.png, Screen Shot 2016-02-25 at 11.41.58.png
>
>
> When I create new remote server in teiid designer, try to connect to it and refresh the connection an exception occurs. After clicking OK in the alert dialogue connection to server works.
> When I hit refresh once more, there is no exception/error.
> Screenshots attached
> Exception:
> {code:java}
> org.teiid.adminapi.AdminComponentException: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1761)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:796)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refresh(ExecutionAdmin.java:722)
> at org.teiid.runtime.client.admin.ExecutionAdmin.connect(ExecutionAdmin.java:682)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:253)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:89)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:132)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.jboss.reddeer.core.handler.WidgetHandler$5.run(WidgetHandler.java:382)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:194)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1756)
> ... 72 more
> Caused by: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:115)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:123)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 74 more
> {code}
> TD 10.0.0.Beta3
> DV 6.2
> remote connection using ssh
> the connection uses management operations
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2794) Connecting to remote server and refreshing produces an exception
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2794?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2794:
-----------------------------------
Fix Version/s: (was: 11.2)
> Connecting to remote server and refreshing produces an exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2794
> URL: https://issues.jboss.org/browse/TEIIDDES-2794
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Attachments: Screen Shot 2016-02-25 at 11.31.43.png, Screen Shot 2016-02-25 at 11.41.58.png
>
>
> When I create new remote server in teiid designer, try to connect to it and refresh the connection an exception occurs. After clicking OK in the alert dialogue connection to server works.
> When I hit refresh once more, there is no exception/error.
> Screenshots attached
> Exception:
> {code:java}
> org.teiid.adminapi.AdminComponentException: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1761)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:796)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refresh(ExecutionAdmin.java:722)
> at org.teiid.runtime.client.admin.ExecutionAdmin.connect(ExecutionAdmin.java:682)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:253)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:89)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:132)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.jboss.reddeer.core.handler.WidgetHandler$5.run(WidgetHandler.java:382)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:194)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1756)
> ... 72 more
> Caused by: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:115)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:123)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 74 more
> {code}
> TD 10.0.0.Beta3
> DV 6.2
> remote connection using ssh
> the connection uses management operations
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2755) No Quick fix offered after importing VDB with same models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2755?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2755.
------------------------------------
Fix Version/s: (was: 11.2)
Resolution: Won't Fix
> No Quick fix offered after importing VDB with same models
> ---------------------------------------------------------
>
> Key: TEIIDDES-2755
> URL: https://issues.jboss.org/browse/TEIIDDES-2755
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Assignee: Barry LaFond
> Attachments: QT_Greenplum_Push.vdb, QT_MySql50_Push.vdb, Screen Shot 2016-01-12 at 9.57.25 (2).png, Screen Shot 2016-01-12 at 9.57.48 (2).png, Screen Shot 2016-01-12 at 9.58.00 (2).png
>
>
> I have 2 VDBs with models that have same names. After importing the first one and extracting the models, TD doesn't offer this option for the second VDB in second project.
> I can see that the warning says that models are not in +workspace+, but I think TD should check if models are in the +project folder+ not in workspace.
> In the screenshots, you can see that there is no warning for NewProject2.
> VDBs attached.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2776) Preview fails for file source table after a Server stop and restart
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2776?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2776:
-----------------------------------
Fix Version/s: 11.3
(was: 11.2)
> Preview fails for file source table after a Server stop and restart
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2776
> URL: https://issues.jboss.org/browse/TEIIDDES-2776
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, Patch Release
> Affects Versions: 9.0.3
> Reporter: Debbie Steigner
> Assignee: Paul Richardson
> Fix For: 11.3
>
> Attachments: TestModelProjectSet.zip, testcsv.csv
>
>
> I have only seen this with a flat file source, standard jdbc database tables only need the "Refresh/Reconnect Teiid Instance Connection" button to refresh and have previews work again.
> Setup a Remote Server in JBDS
> select Server externally managed
> Remote and Remote Management Commands
> * Create a new model project, add a File source
> * Create a view model and do a preview on the view table
> That works! Great.
> Then:
> * We right-click the server and press Stop. Then press Start
> * Now when you try to preview again, it fails. The EAP server is in a reload-required state and the below error is shown in Designer log and a pop-up:
> !ENTRY org.teiid.designer.dqp.ui 4 0 2016-02-05 13:37:38.436
> !MESSAGE JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.file]
> !STACK 0
> org.teiid.adminapi.AdminProcessingException: JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.file]
> at org.teiid.runtime.client.admin.v8.Admin8Factory$ResultCallback.onFailure(Admin8Factory.java:202)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.cliCall(Admin8Factory.java:1591)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.addModuleResourceAdapter(Admin8Factory.java:397)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.createConnectionFactory(Admin8Factory.java:303)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.createDataSource(Admin8Factory.java:497)
> at org.teiid.runtime.client.admin.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:373)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:614)
> at org.teiid.designer.runtime.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:177)
> at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:527)
> at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1365)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> !ENTRY org.teiid.designer.ui 4 0 2016-02-05 13:37:38.863
> !MESSAGE Error running preview. See log for more information.
> !STACK 1
> org.eclipse.core.runtime.CoreException: Error running preview. See log for more information.
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:106)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.run(PreviewDataWorker.java:255)
> at org.teiid.designer.runtime.ui.preview.PreviewTableDataContextAction.run(PreviewTableDataContextAction.java:99)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> 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$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Contains: * JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.file]
> !SUBENTRY 1 org.teiid.designer.ui 4 4 2016-02-05 13:37:38.864
> !MESSAGE Error running preview. See log for more information.
> !SUBENTRY 2 org.teiid.designer.ui 4 0 2016-02-05 13:37:38.864
> !MESSAGE * JBAS010473: Failed to load module for RA [org.jboss.teiid.resource-adapter.file]
> To fix it:
> * We run a :reload on the EAP server with jboss-cli
> * Then preview works again.
> So, desired fix, when the server is in a reload-required state, reload the server or at least prompt for it instead of erroring out.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2724) [Usability] Importing DDL that has unsupported syntax is not indicated in error message
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2724?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2724:
-----------------------------------
Fix Version/s: Future
(was: 11.2)
> [Usability] Importing DDL that has unsupported syntax is not indicated in error message
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2724
> URL: https://issues.jboss.org/browse/TEIIDDES-2724
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export, ModeShape Integration
> Affects Versions: 9.0.3
> Reporter: Van Halbert
> Assignee: Dan Florian
> Fix For: Future
>
>
> Importing DDL that contains unsupported syntax produces the following "Import Messages":
> - 2 instances of a DDL statement of type [ddl:ddlProblem] were found, but cannot be processed
> This message doesn't give any indication as to which statement (s) are the issue. And didn't find any message(s) in the .log file either. It would be better if "ddl:ddlProblem" was replaced with the first "x" number of characters from the statement that was identified as a problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (TEIIDDES-2716) Improve importing of dynamic VDBs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2716?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2716:
-----------------------------------
Fix Version/s: Future
(was: 11.2)
> Improve importing of dynamic VDBs
> ---------------------------------
>
> Key: TEIIDDES-2716
> URL: https://issues.jboss.org/browse/TEIIDDES-2716
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dynamic VDBs, VDB & Execution
> Reporter: Matus Makovy
> Fix For: Future
>
>
> If you want to import dynamic VDB now, you have to import a file to a project and then right-click the dynamic VDB and select Modeling -> Generate VDB archive and models.
> I thnik it could be more user friendly. For example there could be an option to import dynamic VDB using: File -> Import -> Dynamic VDB. One wizard would guide you through the whole import of the vdb xml file to the project.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months