August 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1849) how to connect the excel file using the odbc driver

by Ramc Natarajan (JIRA)

Ramc Natarajan created TEIIDDES-1849: ---------------------------------------- Summary: how to connect the excel file using the odbc driver Key: TEIIDDES-1849 URL: https://issues.jboss.org/browse/TEIIDDES-1849 Project: Teiid Designer Issue Type: Task Reporter: Ramc Natarajan -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1848) Preview fails after manual undeployment of the preview vdb

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1848: --------------------------------------- Summary: Preview fails after manual undeployment of the preview vdb Key: TEIIDDES-1848 URL: https://issues.jboss.org/browse/TEIIDDES-1848 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 8.2 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.2.x-prod-eds6.0 1) Previewed a model table successfully. 2) Then in the Servers view, manually un-deployed the Preview VDB for the model. 3) After un-deployment, try to re-preview the same table - it fails: org.teiid.jdbc.TeiidSQLException: TEIID40046 VDB "PREVIEW_411a743f-4fdf-4de8-9301-643f89c3926f_TEIIDDES-1693_project" version "latest" does not exist. The preview manager should be able the re-deploy the preview vdb on demand. -- 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

10 years, 8 months

1
0
0 / 0

[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.2.x-prod-eds6.0 > 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.2.x-prod-eds6.0 > > > 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1847) Filter preview vdbs and data sources from Teiid tree if workspace UID different than runtime user

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1847: -------------------------------------- Summary: Filter preview vdbs and data sources from Teiid tree if workspace UID different than runtime user Key: TEIIDDES-1847 URL: https://issues.jboss.org/browse/TEIIDDES-1847 Project: Teiid Designer Issue Type: Enhancement Components: Data Preview, Teiid Integration Affects Versions: 8.2.x-prod-eds6.0 Reporter: Barry LaFond Assignee: Paul Richardson Fix For: 8.2.x-prod-eds6.0 A shared server may end up containing preview artifacts from different users. Filter out any preview VDB and Data Sources that do not contain the current user's workspace UID (identifier) -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1835) Add preview artifact management actions

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1835?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1835: ----------------------------------------- 1) yes, I think it should only show those that match the users workspace. Preview was intended to be hidden for the most part, so I think they should not see others preview artifacts 3) I'd vote 'no' on adding the actions to the modeling list. No need to clutter it up more, and we should just do the cleanup automatically. > Add preview artifact management actions > --------------------------------------- > > Key: TEIIDDES-1835 > URL: https://issues.jboss.org/browse/TEIIDDES-1835 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > Seems like it would be beneficial to have a couple of preview artifact management actions. > Clear Preview Artifacts > Refresh Preview Artifacts > The fix for TEIIDDES-1833 probably require the code to perform the "Clear" operation anyway. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1835) Add preview artifact management actions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1835?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1835: ---------------------------------------- Some related thoughts... 1) Server can have preview artifacts belonging to multiple users * Should Teiid tree view only those preview artifacts that match the users "workspace UID" ? 2) Could add actions to Teiid Instance actions list (add to Show Preview VDB/Data Sources actions list drop-down) * Clear Preview Artifacts opens dialog with "VDBs" and/or "Data Sources" 3) Add actions to Modeling action list if selecting Project? * Clear Preview Artifacts * Refresh Preview Artifacts > Add preview artifact management actions > --------------------------------------- > > Key: TEIIDDES-1835 > URL: https://issues.jboss.org/browse/TEIIDDES-1835 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > Seems like it would be beneficial to have a couple of preview artifact management actions. > Clear Preview Artifacts > Refresh Preview Artifacts > The fix for TEIIDDES-1833 probably require the code to perform the "Clear" operation anyway. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1845) Remove Designer's Help plugin from this branch

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1845?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1845. ------------------------------------ Resolution: Done Done > Remove Designer's Help plugin from this branch > ---------------------------------------------- > > Key: TEIIDDES-1845 > URL: https://issues.jboss.org/browse/TEIIDDES-1845 > Project: Teiid Designer > Issue Type: Task > Components: Documentation > Affects Versions: 8.2.x-prod-eds6.0 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2.x-prod-eds6.0 > > > The Designer TOC/Help plugin reflects community documentation. > Product documentation will be handled via JBoss Central links to JBoss Data Virtualization tooling -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1846) Top Down modeling, when importing to create views, allow for default syntax to applied

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1846: ------------------------------------- Summary: Top Down modeling, when importing to create views, allow for default syntax to applied Key: TEIIDDES-1846 URL: https://issues.jboss.org/browse/TEIIDDES-1846 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Van Halbert Assignee: Barry LaFond When a user is starting from a top-down approach (building the views) to design their data layers, and will be performing an import to create the view layer, it would speed up the iterative development of build / deploy / test (not preview) if when the view is built (on import), it can contain valid syntax so that the model will validate. Example of syntax could be, "Select '1'" or "Select 'view not defined'" or throw an exception. This would enable the modeler to implement the views at their pace and have it deployable, rather than having to go thru every view and add syntax before its valid. This is akin to JAVA and NOOP'ing the methods. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1843) could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1843?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-1843: ----------------------------------------------- Agreeing with [~phantomjinx] - it makes no sense to add these associate sites to the sub-components sites we got today.. If they need to be exposed as single click installs we need a separate site that can aggregate all the right parts (but that is exactly what the main JBT and JBTIS sites are for). > could installation of Teiid Designer be made simpler via p2 metadata <references> to upstream sites? > ---------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1843 > URL: https://issues.jboss.org/browse/TEIIDDES-1843 > Project: Teiid Designer > Issue Type: Bug > Components: Build, Documentation, Usability > Affects Versions: 8.2 > Reporter: Nick Boldt > Assignee: Paul Richardson > Fix For: 8.3 > > Attachments: TEIIDDES1843.png, TEIIDDES1843_2.png > > > Current instructions for installing Teiid Designer 8.2 [1] involve multiple steps, installs, and restarts of Eclipse. This is more complex than it needs to be. > [1] https://www.jboss.org/teiiddesigner/downloads > Instead, the Teiid Designer update site could simply reference the upstream URLs that it needs to perform the installation, and as long as all of Teiid Designer's features & plugins properly define dependencies on the required upstream features and plugins on these update sites, installation should be able to proceed from a single URL, rather than a handful. It would allow installation via a single step, rather than several iterative steps. > I'll attach a PR to demonstrate this. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1845) Remove Designer's Help plugin from this branch

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1845: -------------------------------------- Summary: Remove Designer's Help plugin from this branch Key: TEIIDDES-1845 URL: https://issues.jboss.org/browse/TEIIDDES-1845 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 8.2.x-prod-eds6.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2.x-prod-eds6.0 The Designer TOC/Help plugin reflects community documentation. Product documentation will be handled via JBoss Central links to JBoss Data Virtualization tooling -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2013