April 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1305) Add Support for SAP Annotations

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1305: ----------------------------------- Summary: Add Support for SAP Annotations Key: TEIIDDES-1305 URL: https://issues.jboss.org/browse/TEIIDDES-1305 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.7 Reporter: Ted Jones Fix For: 8.0 Need to support SAP annotations for accessing SAP Gateway services. This may require adding the SAP OData SDK to the Designer. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1090) Usability:Confusion in the View model, create a base table or a view table

by Van Halbert (Created) (JIRA)

Usability:Confusion in the View model, create a base table or a view table -------------------------------------------------------------------------- Key: TEIIDDES-1090 URL: https://issues.jboss.org/browse/TEIIDDES-1090 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.4.2 Reporter: Van Halbert In the view model, there really isn't any feature/functional difference for which one should be recommended over the other. The only difference I see is that the view table doesn't have the ability to create indexes/keys as the base table. Which brings in the question, do we really need two way's to create a view table, regardless what we call it? -- 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

14 years

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-837) NPEs found in Designer log after testing SalesForce

by Paul Nittel (JIRA)

NPEs found in Designer log after testing SalesForce --------------------------------------------------- Key: TEIIDDES-837 URL: https://issues.jboss.org/browse/TEIIDDES-837 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Paul Nittel Attachments: NpeUhOh.log, NpeUhOh_MPS.zip While testing the SalesForce importer, I noticed I was getting a new NPE each time I clicked in the Model explorer tree. I don't know when it started, so I can't say what may have triggered it. But in the hope that you may find something, I've attached the exported log. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-375) Clone Project clones everything except VDBs

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-375?page=com.atlassian.jira.plug... ] Mark Drilling resolved TEIIDDES-375. ------------------------------------ Resolution: Won't Fix closing this - outdated - we dont have a clone project action anymore > Clone Project clones everything except VDBs > ------------------------------------------- > > Key: TEIIDDES-375 > URL: https://issues.jboss.org/browse/TEIIDDES-375 > Project: Teiid Designer > Issue Type: Bug > Environment: RHEL & Fedora 7 > Reporter: Paul Nittel > Assignee: Barry LaFond > > I right-clicked on an open project (that contained a VDB, in addition to the other models) and selected Clone Project. When finished, the cloned project was identical, except it had no VDB. > I looked at the requirements for "Clone Project" and didn't see anything about not cloning VDBs. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1196) default criteria based on PK/FK relations should be included when adding tables to transformations

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1196?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1196: ------------------------------------ Assignee: Mark Drilling Fix Version/s: 7.8 Affects Version/s: 7.6 Component/s: Transformations > default criteria based on PK/FK relations should be included when adding tables to transformations > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1196 > URL: https://issues.jboss.org/browse/TEIIDDES-1196 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations > Affects Versions: 7.6 > Reporter: Marc Shirley > Assignee: Mark Drilling > Priority: Optional > Fix For: 7.8 > > > Default transformation SQL when two tables with PK/FK relationship are joined (by pressing "add" button in Designer to add tables to transformation) should include default criteria specifying join on the PK/FK relationship. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-949) Usability: Use FK/PK relationships to prebuild JOIN when building view

by Van Halbert (JIRA)

Usability: Use FK/PK relationships to prebuild JOIN when building view ----------------------------------------------------------------------- Key: TEIIDDES-949 URL: https://issues.jboss.org/browse/TEIIDDES-949 Project: Teiid Designer Issue Type: Enhancement Components: Modeling, Views Affects Versions: 7.1.1 Reporter: Van Halbert When creating a new view which includes two tables which do have FK/PK relationship defined (as links), the view should automatically add the JOIN clause. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-293) WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-293?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-293. ----------------------------------- Resolution: Out of Date New WSDL to relational importer now handles complex types and allows users to modify result-set column datatypes > WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names. > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-293 > URL: https://issues.jboss.org/browse/TEIIDDES-293 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1, 7.2, 7.3 > Reporter: John Doyle > Assignee: Barry LaFond > Labels: wsdltorelational > Fix For: 7.7.1 > > Attachments: TmsWebService.wsdl > > > The attached WSDL causes an NPE when the model objects are being created. -- 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

14 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-276) improve WSDL importer accuracy

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-276?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-276. ----------------------------------- Resolution: Out of Date REcent improvements in WSDL importer has addressed this issue > improve WSDL importer accuracy > ------------------------------- > > Key: TEIIDDES-276 > URL: https://issues.jboss.org/browse/TEIIDDES-276 > Project: Teiid Designer > Issue Type: Task > Components: Import/Export > Reporter: Marc Shirley > Fix For: 7.7.1, Future > > > are we trying to do too much ourselves instead of leveraging some standard open source components - seems like somebody must have solved the problem of turn WSDL into accurate Java object heirarchy, and we can go from there... -- 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

14 years

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-1118: ------------------------------------ The fix broke on linux and we double-encoding the URI causing same ArrayIndexOutOfBoundsException. Re-opening > 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.1 > > > 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

14 years

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1118: ----------------------------------- Fix Version/s: 7.7.1 (was: 7.7) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=781036 (was: 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.1 > > > 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

14 years

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 April 2012