August 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1772) DDL Importer - model object update method needs rework in EmfModelGenerator

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1772?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-1772: ----------------------------------------- The issue with handling updates with delete/create is that the 'updated' object will have a new uuid which would then break any any prior references to the object. Need to refine the update scenario so that the existing object is located and the properties changed. All children would also then need to be inspected and updated. > DDL Importer - model object update method needs rework in EmfModelGenerator > --------------------------------------------------------------------------- > > Key: TEIIDDES-1772 > URL: https://issues.jboss.org/browse/TEIIDDES-1772 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > In the EmfModelGenerator, objects are tagged as delete/create/replace. For the replace scenario, it currently does a delete/create. This needs to be changed to actually modify the target object instead of delete and create a new object. This is near line 162 of EmfModelGenerator -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1495) New Source Function action disabled if one already exists in model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1495?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1495: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 996292|https://bugzilla.redhat.com/show_bug.cgi?id=996292] from NEW to ASSIGNED > New Source Function action disabled if one already exists in model > ------------------------------------------------------------------ > > Key: TEIIDDES-1495 > URL: https://issues.jboss.org/browse/TEIIDDES-1495 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7, 7.8 > Reporter: Barry LaFond > Assignee: Dan Florian > Priority: Critical > Fix For: 8.0 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1636) Unable to create multiple source functions under one physical model in Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1636?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1636: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 996292|https://bugzilla.redhat.com/show_bug.cgi?id=996292] from NEW to ASSIGNED > Unable to create multiple source functions under one physical model in Teiid Designer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1636 > URL: https://issues.jboss.org/browse/TEIIDDES-1636 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7 > Reporter: Debbie Steigner > Assignee: Johnathon Lee > Fix For: 7.7.3 > > Attachments: CreatePushdownFunctionAction.java.patch > > > Unable to create multiple source functions under one physical model in EDS Teiid Designer. I want to create multiple source functions say LTRIM, RTRIM, TRUNC etc under one physical model and noticed that once I create the first source function by using (right click on model name -> New Child -> Create Source Function) the "Create Source Function" menu item is no longer available to create others. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1636) Unable to create multiple source functions under one physical model in Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1636?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1636: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=928788, https://bugzilla.redhat.com/show_bug.cgi?id=996292 (was: https://bugzilla.redhat.com/show_bug.cgi?id=928788) > Unable to create multiple source functions under one physical model in Teiid Designer > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1636 > URL: https://issues.jboss.org/browse/TEIIDDES-1636 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7 > Reporter: Debbie Steigner > Assignee: Johnathon Lee > Fix For: 7.7.3 > > Attachments: CreatePushdownFunctionAction.java.patch > > > Unable to create multiple source functions under one physical model in EDS Teiid Designer. I want to create multiple source functions say LTRIM, RTRIM, TRUNC etc under one physical model and noticed that once I create the first source function by using (right click on model name -> New Child -> Create Source Function) the "Create Source Function" menu item is no longer available to create others. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1816) VDB datasource contains incorrect connection url

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1816?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1816: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=993585 > VDB datasource contains incorrect connection url > ------------------------------------------------ > > Key: TEIIDDES-1816 > URL: https://issues.jboss.org/browse/TEIIDDES-1816 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.7.4 > Environment: JBDS 5.0.2.GA, Teiid Designer 7.7.4, java oracle jdk6 1.6.0_45, SOA 5.3.1.GA, EDS 5 > Reporter: Lucie Fabrikova > > VDB datasource (deploy/mysimplevdb-ds.xml) contains invalid connection url if created via Guides - Create REST WAR: <connection-url>jdbc:teiid:MySimpleVdb.vdb@mm://localhost:31443</connection-url> > Steps to reproduce: > 1. Take any VDB > 2. Modelling actions -> Create REST WAR -> Deploy VDB > 3. In dialog, select the VDB and choose "Create data source" > Next, VDB is deployed and data source for the VDB is created, but contains invalid connection URL. -- 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, 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 Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1779?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1779: --------------------------------------- JBIDE-14592 is about trying to start and manage the server from eclipse. The issue I'm seeing is after externally starting the server, Designer has issues. And looking looking at the message, it appears Designer is not specifying the "domain" (ex., "ha") in its address that its calling. > 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 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1827) The term Teiid Server in Designer should be changed to replace Server with Instance.

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1827: -------------------------------------- Summary: The term Teiid Server in Designer should be changed to replace Server with Instance. Key: TEIIDDES-1827 URL: https://issues.jboss.org/browse/TEIIDDES-1827 Project: Teiid Designer Issue Type: Task Components: Documentation, Teiid Integration Affects Versions: 8.2 Reporter: Barry LaFond Priority: Critical Fix For: 8.2.GA As Teiid's evolved and been integrated into AS7, it's become apparent that Designer's references to a "Teiid Server" is incorrect. Teiid is now a subsystem within the AS environment. We need to convert all display text which refers to Teiid as a "Server" to say "Instance" in stead. Also need to update our docs, Wiki pages including screen caps for 8.2/product docs. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1826) Designer doesn't yet support Flat File Connection Profile URL input option

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1826: -------------------------------------- Summary: Designer doesn't yet support Flat File Connection Profile URL input option Key: TEIIDDES-1826 URL: https://issues.jboss.org/browse/TEIIDDES-1826 Project: Teiid Designer Issue Type: Enhancement Components: Datatools Integration Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Mark Drilling Priority: Critical Fix For: 8.2 Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files. Teiid Designer's Flat File importer only expects the "folder" version. Need to work with a single file URI Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported. Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1825) OData MED not getting picked up in Designer kit

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1825?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1825. ------------------------------------- Resolution: Done The odata.mxd file had not been added to build.properties. I moved both mxd files into a 'meds' folder and changed build.properties to include the folder. https://github.com/Teiid-Designer/teiid-designer/pull/225 > OData MED not getting picked up in Designer kit > ----------------------------------------------- > > Key: TEIIDDES-1825 > URL: https://issues.jboss.org/browse/TEIIDDES-1825 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > The new OData built-in MED is not getting picked up in the 8.2 Designer kit (was not added to the build.properties) -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1825) OData MED not getting picked up in Designer kit

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1825: --------------------------------------- Summary: OData MED not getting picked up in Designer kit Key: TEIIDDES-1825 URL: https://issues.jboss.org/browse/TEIIDDES-1825 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 8.2 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.2 The new OData built-in MED is not getting picked up in the 8.2 Designer kit (was not added to the build.properties) -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2013