September 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1822: ----------------------------------- Assignee: Johnathon Lee (was: Barry LaFond) > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Johnathon Lee > Fix For: 8.3 > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1822) Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1822: ----------------------------------- Assignee: Barry LaFond (was: Johnathon Lee) > Change the way Designer's server framework interprets VDB status to replace Active/Inactive with isValid() check as Status value > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1822 > URL: https://issues.jboss.org/browse/TEIIDDES-1822 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3 > > > 1) Set-up simple JDBC source/model/vdb and test/execute VDB > 2) Delete the Data Source in the Server view > 3) Try and execute the VDB again and get exception logged in console > Seems the active/inactive status is old terminology and Designer should be using the isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent Execute VDB from being launched or at least a warning message check. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1864: ----------------------------------- Assignee: Johnathon Lee (was: Barry LaFond) > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Johnathon Lee > Fix For: 8.3, 7.7.5 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1864: ----------------------------------- Fix Version/s: 7.7.5 > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.3, 7.7.5 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1865) Action Sets data flow incomplete

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1865?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1865. ------------------------------------ Resolution: Done Completed > Action Sets data flow incomplete > -------------------------------- > > Key: TEIIDDES-1865 > URL: https://issues.jboss.org/browse/TEIIDDES-1865 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.3 > > > Noticed in the Remote XML import action set that the Preview Data action is not pre-populated with the generated view table. User has to go select it. > Need to check all the action sets/actions to insure all dialogs and wizards involved are properly checking designerProperties and setting initial values if they can be discovered. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1862) Metamatrix simple-types xsd import prevents generation of cxf war file

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1862?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1862: -------------------------------------- Assignee: Paul Richardson (was: Ted Jones) > Metamatrix simple-types xsd import prevents generation of cxf war file > ---------------------------------------------------------------------- > > Key: TEIIDDES-1862 > URL: https://issues.jboss.org/browse/TEIIDDES-1862 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.2 > Environment: Windows 7, Eclipse Kepler > Reporter: Pablo Navascues > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > > 1. Generate a model to expose through webservices that uses one of the datatypes from the http://www.metamatrix.com/metamodels/SimpleDatatypes-instance schema. > 2. Select the model > Right Click > Modeling > Create Web Service > 3. XSDs generated have the metamatrix schema import which uses "http://www.metamatrix.com/metamodels/SimpleDatatypes-instance" for the namespace AND the schema location. > 4. Double clicking in the model explorer in one of this xsd trys to open it and hangs for a while. > 5. Select VDB > Modelling > Generate JbossWS-CXF War. This hangs for a long while and afterwards fails to generate the war file. > Is there a workaround for 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, 7 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.4 (was: 8.3) > 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.4 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1864: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1011688 > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1864: ----------------------------------- Attachment: DataRoleResolver.patch Fixed target still exists logic to search resource correctly for EObject given model relative path to target object of each permission > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.3 > > Attachments: DataRoleResolver.patch > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1864: ---------------------------------------- The simplistic use-case described above does make sense and the current capability of the VDB Editor is allow creating, editing and managing data roles for a given VDB containing specific versions of models. Renaming a model outside the VDB and synching the VDB poses all sorts of issues and scenarios. In the case above, user renames one column. But what if user renamed BOTH columns. Unless the refactoring (rename actions) operated directly on the VDB (models AND data roles), there no way to handle anything but the "singular change" use-case. > Changes to a table's columns can result in role being reset for the entire model > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1864 > URL: https://issues.jboss.org/browse/TEIIDDES-1864 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.7, 8.2 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.3 > > > I have a model like below with a role defined to remove read privileges on 'column1a2' only. > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> column1b2 > I adjust the model to rename 'column1b2' to 'uselessColumn': > model1 > -> table1a > ---> column1a1 > ---> column1a2 > -> table1b > ---> column1b1 > ---> uselessColumn > The role is reset and now has default read privileges defined across the entire model. I have to manually edit the role to reset it to the prior defined permissions. -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2013