February 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1060) Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1060?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1060: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780888|https://bugzilla.redhat.com/show_bug.cgi?id=780888] from NEW to ASSIGNED > Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1060 > URL: https://issues.jboss.org/browse/TEIIDDES-1060 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 7.7, 7.7.1 > > > Incorrect Transformation when using 'Create XML to Scalar Transformation' in Teiid Designer. See Steps to reproduce section for full description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1118: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=781036 > Add/Remove operations on a VDB should block other operations on the VDB > ----------------------------------------------------------------------- > > Key: TEIIDDES-1118 > URL: https://issues.jboss.org/browse/TEIIDDES-1118 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Marc Shirley > Assignee: Mark Drilling > Fix For: 7.7 > > > As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception: > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435) > at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244) > at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709) > at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > 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.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > 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:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > 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:620) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) > at org.eclipse.equinox.launcher.Main.run(Main.java:1408) > at org.eclipse.equinox.launcher.Main.main(Main.java:1384) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1118: ---------------------------------------------- Bugzilla Update: Perform > Add/Remove operations on a VDB should block other operations on the VDB > ----------------------------------------------------------------------- > > Key: TEIIDDES-1118 > URL: https://issues.jboss.org/browse/TEIIDDES-1118 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Marc Shirley > Assignee: Mark Drilling > Fix For: 7.7 > > > As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception: > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.ArrayIndexOutOfBoundsException: 0 > at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435) > at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244) > at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709) > at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > 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.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > 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:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > 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:620) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) > at org.eclipse.equinox.launcher.Main.run(Main.java:1408) > at org.eclipse.equinox.launcher.Main.main(Main.java:1384) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1228) Create Preview Data Dialog

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1228: -------------------------------------- Summary: Create Preview Data Dialog Key: TEIIDDES-1228 URL: https://issues.jboss.org/browse/TEIIDDES-1228 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 7.7 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.7 Working with Advisor-type view and Action Library View, it seems we need a dialog to handle allowing Preview Data action to be executed WITHOUT pre-selecting a table or procedure. So create a dialog that queries the user to select a table or wizard from the workspace first, then executes the Preview Data action. Probably should include - check for "Server Exists" (i.e. if so, then "ping()" to verify preview could run. - Allow selection of only previewable objects (Tables and procedures) - validate each selection. If "ERROR" then don't allow "OK" or maybe change the "OK" to "Execute"?? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] (TEIIDDES-1236) vdb.xml file model element should have a metamodel class attribute

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1236: -------------------------------------- Summary: vdb.xml file model element should have a metamodel class attribute Key: TEIIDDES-1236 URL: https://issues.jboss.org/browse/TEIIDDES-1236 Project: Teiid Designer Issue Type: Enhancement Components: VDB & Execution Affects Versions: 7.7 Reporter: Barry LaFond Fix For: 7.7 The GenerateWarAction.selectionChanged() method performs a check on the contents of a VDB in order to determine if there are Web Service models in it. This is currently a heavy weight operation that works with ModelResource objects. If the Model element included a metamodelClass="Web Service" value in it, then the check would be much lighter weight operation. Adding a property for Designer's consumption seems pretty straight forward. The vdb-deploy.xsd schema defines the following element within the "model" complex type: <xs:element name="property" type="property" minOccurs="0" maxOccurs="unbounded"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (TEIIDDES-1237) Apostrophe Malfunction in Use Qualified Names tool-tip

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1237: ------------------------------------- Summary: Apostrophe Malfunction in Use Qualified Names tool-tip Key: TEIIDDES-1237 URL: https://issues.jboss.org/browse/TEIIDDES-1237 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.6 Reporter: Paul Nittel Priority: Minor Attachments: SpecifyImportOptions.png On the JDBC importer's Specify Import Options page, the tool-tip for the Use Qualified Names option has the word "it's". It should be "its". ("It's" is the contract of "it is", so the sentence in question reads, "If a catalog is supported and exists for your schema, it is name will be included...". The possessive form of "it" is "its". No apostrophe.) I'll attach a screenshot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1239) SWT Thread access error in DqpUiPlugin shutting down Designer

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1239: -------------------------------------- Summary: SWT Thread access error in DqpUiPlugin shutting down Designer Key: TEIIDDES-1239 URL: https://issues.jboss.org/browse/TEIIDDES-1239 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.7 org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4282) at org.eclipse.swt.SWT.error(SWT.java:4197) at org.eclipse.swt.SWT.error(SWT.java:4168) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Shell.<init>(Shell.java:263) at org.eclipse.swt.widgets.Shell.<init>(Shell.java:359) at org.eclipse.jface.window.Window.createShell(Window.java:487) at org.eclipse.jface.window.Window.create(Window.java:430) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.jface.window.Window.open(Window.java:790) at org.eclipse.jface.dialogs.ProgressMonitorDialog.open(ProgressMonitorDialog.java:678) at org.eclipse.jface.dialogs.ProgressMonitorDialog.aboutToRun(ProgressMonitorDialog.java:579) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:504) at com.metamatrix.modeler.dqp.ui.DqpUiPlugin.stop(DqpUiPlugin.java:195) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1238) NPE opening web service model for editing

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1238: -------------------------------------- Summary: NPE opening web service model for editing Key: TEIIDDES-1238 URL: https://issues.jboss.org/browse/TEIIDDES-1238 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.7 While opening a WS operation for editing after start-up, received the following: java.lang.NullPointerException at org.teiid.query.resolver.util.ResolverVisitor.findWithImplicitConversions(ResolverVisitor.java:574) at org.teiid.query.resolver.util.ResolverVisitor.resolveFunction(ResolverVisitor.java:518) at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:352) at org.teiid.query.sql.symbol.Function.acceptVisitor(Function.java:182) at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:52) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:140) at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:276) at org.teiid.query.sql.symbol.Function.acceptVisitor(Function.java:182) at org.teiid.query.sql.navigator.PostOrderNavigator.doVisit(PostOrderNavigator.java:40) at org.teiid.query.resolver.util.ResolverVisitor.resolveLanguageObject(ResolverVisitor.java:1012) at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveStatement(UpdateProcedureResolver.java:253) at org.teiid.query.resolver.command.UpdateProcedureResolver.resolveBlock(UpdateProcedureResolver.java:164) ..... Looks like the logic in UdfManager.getFunctionLibrary() needs some tweaking because the first time it's called, changed == FALSE public synchronized FunctionLibrary getFunctionLibrary() { //System.out.println("UdfManger.getFunctionLibrary()"); if( !changed ) { return this.cachedFunctionLibrary; } change to: public synchronized FunctionLibrary getFunctionLibrary() { //System.out.println("UdfManger.getFunctionLibrary()"); if( !changed && this.cachedFunctionLibrary != null ) { return this.cachedFunctionLibrary; } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1225) 'Add MED to Registry' action allows attempt to add an invalid MED to the registry

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1225: --------------------------------------- Summary: 'Add MED to Registry' action allows attempt to add an invalid MED to the registry Key: TEIIDDES-1225 URL: https://issues.jboss.org/browse/TEIIDDES-1225 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 7.7 Reporter: Mark Drilling The 'Add MED to Registry' action looks at the mxd problem markers before doing the add operation. However, if the workspace has not been built the file may not have a problem marker. This results in attempt to add an invalid MED to the registry. We should not allow the process to get that far - ensure the build is complete or check for errors in a different manner. Example usage is in ModelExtensionDefinitionEditor.createActions, which uses RegistryDeploymentValidator.checkProblemMarkers to do this check currently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2012