[JBoss JIRA] (TEIIDDES-1779) Designer error when trying to read a remote server configuration that's running in domain mode
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1779?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1779:
-----------------------------------
Fix Version/s: 8.5
(was: 8.4)
Pushing again since JBDS still does not support domain mode
> Designer error when trying to read a remote server configuration that's running in domain mode
> ----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1779
> URL: https://issues.jboss.org/browse/TEIIDDES-1779
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.5
>
>
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:58)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.getTeiidRuntimeVersion(JBoss7ServerUtil.java:172)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.createJboss7TeiidServer(TeiidServerAdapterFactory.java:204)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:185)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:78)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:66)
> 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:474)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:266)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:463)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:432)
> at org.eclipse.wst.server.ui.internal.editor.ServerEditor.doSave(ServerEditor.java:389)
> at org.eclipse.ui.internal.DefaultSaveable.doSave(DefaultSaveable.java:54)
> at org.eclipse.ui.Saveable.doSave(Saveable.java:214)
> at org.eclipse.ui.internal.SaveableHelper.doSaveModel(SaveableHelper.java:348)
> at org.eclipse.ui.internal.WorkbenchPage$11.run(WorkbenchPage.java:3633)
> at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1812)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1809)
> at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284)
> at org.eclipse.ui.internal.WorkbenchPage.saveAll(WorkbenchPage.java:3644)
> at org.eclipse.ui.internal.WorkbenchPage.saveAllEditors(WorkbenchPage.java:3440)
> at org.eclipse.ui.internal.handlers.SaveAllHandler.execute(SaveAllHandler.java:47)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> 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:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-attribute" for [{"subsystem" => "teiid"}]. Failure was "JBAS014883: No resource definition is registered for address [(\"subsystem\" => \"teiid\")]".
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:327)
> ... 76 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2074) Improve the Teiid Connection importer usability
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2074:
-------------------------------------
Summary: Improve the Teiid Connection importer usability
Key: TEIIDDES-2074
URL: https://issues.jboss.org/browse/TEIIDDES-2074
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Van Halbert
Teiid Connection importer needs to be easier to use. Currently, the user has to open the documentation to know what properties to enter so that, for example, the jdbc import is filtering on tables types, schemas, etc. Otherwise, the importer will grab everything. For JDBC, it should be as easy as the current JDBC importer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2064) Issues with 8.4 Designers handling of Teiid 8.6 Runtime version
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2064?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-2064.
---------------------------------------
Resolution: Done
Changes made:
* Upon connection the teiid instance model in Designer updates the version number from the teiid instance itself
* The teiid instance editor allows editing of the version number when the instance is stopped but not only is it updated upon connection but the field becomes read-only since the instance has told the client what it is rather than a manual guess by the user.
> Issues with 8.4 Designers handling of Teiid 8.6 Runtime version
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2064
> URL: https://issues.jboss.org/browse/TEIIDDES-2064
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.4
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.4
>
>
> * Teiid Designer code-base reflects Teiid 8.6 runtime codebase.
> * Creating a New Server based on EAP 6.1 Alpha 1 with Teiid 8.6 installed results in a TeiidServer who's version is 8.4.0 because TeiidJboss7ServerUtil.getTeiidRuntimeVersion() is returning the DEFAULT_TEIID_8_SERVER which is currently set to 8.4.0 because the server isn't started.
> * Once I start the server I would expect that the server version would be discovered from the actual server connection and re-set to it's real 8.6.0 version, but it's not, it remains at 8.4.0
> * Note we haven't addressed the this use-case fully.
> * VDB's are tagged with a Teiid runtime validation version
> * If no server is running, should the default Teiid version be set to an actual Default version rather than the last selected TeiidServer version value?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2014) 8.4 Release Work
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2014?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-2014:
-------------------------------------------
* Commits cherry-picked to 8.3.x branch and pushed
* New branches in Designer's Teiid fork created to accommodate cherry-picked commits:
** D8.3.x-T7.7.x
** D8.3.x-T8.3.x
** D8.3.x-T8.4.x
> 8.4 Release Work
> ----------------
>
> Key: TEIIDDES-2014
> URL: https://issues.jboss.org/browse/TEIIDDES-2014
> Project: Teiid Designer
> Issue Type: Task
> Components: Release Work
> Affects Versions: 8.4
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.4, 8.3.2
>
>
> Work related to 8.4.0 release including:
> * Version upgrades
> * Copyright changes
> * build/publish
> * documentation
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2072) Teiid connection import generates invalid DDL for hsql data source
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2072?page=com.atlassian.jira.plu... ]
Lucie Fabrikova updated TEIIDDES-2072:
--------------------------------------
Attachment: hsqlDDL.ddl
> Teiid connection import generates invalid DDL for hsql data source
> ------------------------------------------------------------------
>
> Key: TEIIDDES-2072
> URL: https://issues.jboss.org/browse/TEIIDDES-2072
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.1
> Environment: JBTIS 4.1.3.Final, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19
> Reporter: Lucie Fabrikova
> Attachments: ds1.script, hsqlDDL.ddl
>
>
> Teiid importer teiid connection >> source model generates invalid DDL for HSQL data source.
> Message: The DDL failed to parse with message:
> "Unparsable options clause". - The problem line is highlighted below (if found). IS_NULLABLE string(3) OPTIONS (ANNOTATION 'is column nullable?: { YES (might allow) | NO (definitely not) | '''' (unknown) }', NAMEINSOURCE '"IS_NULLABLE"', NATIVE_TYPE 'VARCHAR'),
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2071) Teiid connection import timeouts for oracle, salesforce data sources
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2071?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2071:
-----------------------------------------
The timeout can be extended via preferences. Go to prefs > Teiid Designer page, increase the timeout and retry.
2mins is usually enough, but some sources can take a long time depending on schema size and other factors. We don't recommend using the Teiid Connection Importer for JDBC sources like oracle, where the standard JDBC importer can do a better job.
> Teiid connection import timeouts for oracle, salesforce data sources
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2071
> URL: https://issues.jboss.org/browse/TEIIDDES-2071
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.1
> Environment: JBTIS 4.1.3.Final, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
>
> Teiid importer teiid connection >> source model fails for oracle and salesforce data sources, with "Loading did not complete within 120 sec for VDB: "importVDB". The error log is empty, the server log for oracle:
> 14:47:58,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
> 14:47:58,326 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 3/4/14 2:47 PM
> 14:47:58,447 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 14:50:15,641 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50026 VDB "importVDB.1[importVDBSrcModel{importVDBSrcModel=importVDBSrcModel, oracle, java:/oracle}]" undeployed.
> 14:50:15,651 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment importVDB-vdb.xml (runtime-name: importVDB-vdb.xml) in 17ms
> 14:50:15,744 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014901: Content removed from location /home/lfabriko/Work/tools/DV-6.0.0.GA-redhat-4/server03/jboss-eap-6.1/standalone/data/content/2b/cf8c1e1f29d03c6541693843b60a33d5b30747/content
> 14:50:15,745 INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018558: Undeployed "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2071) Teiid connection import timeouts for oracle, salesforce data sources
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2071?page=com.atlassian.jira.plu... ]
Mark Drilling reassigned TEIIDDES-2071:
---------------------------------------
Assignee: Mark Drilling
> Teiid connection import timeouts for oracle, salesforce data sources
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2071
> URL: https://issues.jboss.org/browse/TEIIDDES-2071
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.1
> Environment: JBTIS 4.1.3.Final, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
>
> Teiid importer teiid connection >> source model fails for oracle and salesforce data sources, with "Loading did not complete within 120 sec for VDB: "importVDB". The error log is empty, the server log for oracle:
> 14:47:58,281 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
> 14:47:58,326 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50029 VDB importVDB.1 model "importVDBSrcModel" metadata is currently being loaded. Start Time: 3/4/14 2:47 PM
> 14:47:58,447 INFO [org.jboss.as.server] (management-handler-thread - 8) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml")
> 14:50:15,641 INFO [org.teiid.RUNTIME] (MSC service thread 1-6) TEIID50026 VDB "importVDB.1[importVDBSrcModel{importVDBSrcModel=importVDBSrcModel, oracle, java:/oracle}]" undeployed.
> 14:50:15,651 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment importVDB-vdb.xml (runtime-name: importVDB-vdb.xml) in 17ms
> 14:50:15,744 INFO [org.jboss.as.repository] (management-handler-thread - 5) JBAS014901: Content removed from location /home/lfabriko/Work/tools/DV-6.0.0.GA-redhat-4/server03/jboss-eap-6.1/standalone/data/content/2b/cf8c1e1f29d03c6541693843b60a33d5b30747/content
> 14:50:15,745 INFO [org.jboss.as.server] (management-handler-thread - 5) JBAS018558: Undeployed "importVDB-vdb.xml" (runtime-name: "importVDB-vdb.xml")
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-2040) Create WS action results in SQL transformation validation errors
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2040?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2040.
------------------------------------
Resolution: Done
The reconcile method checks status of the t-root. If it's invalid it will not reconcile. Added a post processor in the wizard to remove the cached status for the new operations before calling the reconcile attributes method, then saving WS model.
Fixed
> Create WS action results in SQL transformation validation errors
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2040
> URL: https://issues.jboss.org/browse/TEIIDDES-2040
> Project: Teiid Designer
> Issue Type: Bug
> Components: Validation, Web Services Support
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.4, 8.3.2
>
>
> 1) Create/Import a simple Source Model (Parts Supplier Oracle)
> 2) Select model, right-click select Modeling > Create Web Service
> 3) Resulting WS model will have operations with SQL validation errors
> 4) Double-clicking each operation to open it's t-Editor will tweak the SQL and fix the error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month