June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-405) Provide one or more views for Teiid Server Management

by Barry LaFond (JIRA)

Provide one or more views for Teiid Server Management ----------------------------------------------------- Key: TEIIDDES-405 URL: https://jira.jboss.org/jira/browse/TEIIDDES-405 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Provide one or more views for Server Management With new paradigm of "servers" within Designer and working with JBTools the requirement of a Designer "Servers" view was created. It is envisioned that this view should combine as a minimum the Teiid Server, Connector Types, Connectors, Source Bindings and Deployed VDB's - ? One view for all types (JBoss/EAP/Teiid/ModeShape, etc....) - ? or one for each type - WTP Server View?? - add Refresh button/action - Teiid Server View. So the basic view will contain a tree of Teiid Servers who's children include: - SERVER 1)CONNECTOR TYPE - CONNECTORS - SOURCES 2)VDB's (Stretch goal) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-479) Cannot open transformation editor: Unhandled event loop exception - Could not initialize class com.metamatrix.query.internal.ui.sqleditor.sql.SqlSyntax

by Paul Nittel (JIRA)

Cannot open transformation editor: Unhandled event loop exception - Could not initialize class com.metamatrix.query.internal.ui.sqleditor.sql.SqlSyntax ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-479 URL: https://jira.jboss.org/browse/TEIIDDES-479 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Environment: Teiid Designer 7.0.0, Fedora 12, Sun JDK Reporter: Paul Nittel Simple steps to reproduce: 1 - Create a model project 2 - Import a source (I used Parts) 3 - Create a relational view model 4 - Open transformation diagram 5 - Add a single table 6 - Right-click the T-node > Edit At this point, I get the following: Error 2010-06-25 09:52:13.632 Unhandled event loop exception java.lang.NoClassDefFoundError: Could not initialize class com.metamatrix.query.internal.ui.sqleditor.sql.SqlSyntax at com.metamatrix.query.internal.ui.sqleditor.sql.SqlCodeScanner.<init>(SqlCodeScanner.java:114) at com.metamatrix.query.internal.ui.sqleditor.SqlSourceViewerConfiguration.getPresentationReconciler(SqlSourceViewerConfiguration.java:99) at com.metamatrix.query.internal.ui.sqleditor.SqlTextViewer.<init>(SqlTextViewer.java:79) at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.init(SqlEditorPanel.java:266) at com.metamatrix.query.ui.sqleditor.SqlEditorPanel.<init>(SqlEditorPanel.java:239) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.createEditorPanel(TransformationObjectEditorPage.java:691) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.createSelectTabForUpdate(TransformationObjectEditorPage.java:366) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.createCTabFolderWithUpdateTabs(TransformationObjectEditorPage.java:341) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.createControl(TransformationObjectEditorPage.java:308) at com.metamatrix.modeler.internal.ui.editors.ModelObjectEditorPanel.addModelObjectEditor(ModelObjectEditorPanel.java:126) at com.metamatrix.modeler.internal.ui.editors.ModelObjectEditorPanel.activateModelObjectEditor(ModelObjectEditorPanel.java:149) at com.metamatrix.modeler.internal.ui.editors.MultiPageModelEditor.editModelObject(MultiPageModelEditor.java:387) at com.metamatrix.modeler.ui.editors.ModelEditorManager.updateObjectEditor(ModelEditorManager.java:696) at com.metamatrix.modeler.ui.editors.ModelEditorManager$5.run(ModelEditorManager.java:241) at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80) at com.metamatrix.modeler.ui.editors.ModelEditorManager.open(ModelEditorManager.java:234) at com.metamatrix.modeler.ui.editors.ModelEditorManager$7.run(ModelEditorManager.java:401) at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80) at com.metamatrix.modeler.ui.editors.ModelEditorManager.edit(ModelEditorManager.java:393) at com.metamatrix.modeler.ui.editors.ModelEditorManager.edit(ModelEditorManager.java:381) at com.metamatrix.modeler.transformation.ui.part.TransformationEditPart.edit(TransformationEditPart.java:92) at com.metamatrix.modeler.diagram.ui.editor.DiagramSelectionHandler$1.run(DiagramSelectionHandler.java:260) at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80) at com.metamatrix.modeler.diagram.ui.editor.DiagramSelectionHandler.handleDoubleClick(DiagramSelectionHandler.java:258) at com.metamatrix.modeler.transformation.ui.part.TransformationEditPart.performRequest(TransformationEditPart.java:111) at com.metamatrix.modeler.diagram.ui.util.SelectionTracker.handleDoubleClick(SelectionTracker.java:72) at org.eclipse.gef.tools.AbstractTool.mouseDoubleClick(AbstractTool.java:955) at org.eclipse.gef.tools.SelectionTool.mouseDoubleClick(SelectionTool.java:501) at org.eclipse.gef.EditDomain.mouseDoubleClick(EditDomain.java:208) at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseDoubleClicked(DomainEventDispatcher.java:285) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseDoubleClick(LightweightSystem.java:508) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:183) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-462) VDB Editor missing "translator-name" column in model entry table

by Barry LaFond (JIRA)

VDB Editor missing "translator-name" column in model entry table ---------------------------------------------------------------- Key: TEIIDDES-462 URL: https://jira.jboss.org/browse/TEIIDDES-462 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Priority: Blocker Fix For: 7.0 Due to changes in the Teiid connector framework and the vdb.xml schema a "translator-name" requires being exposed to the user for editing/setting prior to VDB deployment. So a new column needs to be added to the editor with appropriate changes to the Vdb model framework. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-404) Facilitate deployment of VDB's from Designer to Teiid Server

by Barry LaFond (JIRA)

Facilitate deployment of VDB's from Designer to Teiid Server ------------------------------------------------------------ Key: TEIIDDES-404 URL: https://jira.jboss.org/jira/browse/TEIIDDES-404 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 As part of 7.0 Teiid integration, both Preview Data and VDB Execution are going to required deployment of workspace VDB's to Teiid. This can be done by Right-click VDB "Deploy to Teiid" action or DND to Teiid Server in Server/Execution View -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-383) Connector Binding/Connector Type property name display is inconsistent.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-383?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-383. ----------------------------------- Resolution: Rejected Design has changed. No Connector Types. Irrelevant defect. > Connector Binding/Connector Type property name display is inconsistent. > ----------------------------------------------------------------------- > > Key: TEIIDDES-383 > URL: https://jira.jboss.org/browse/TEIIDDES-383 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer on Linux, Windows > Reporter: John Doyle > Assignee: Dan Florian > Priority: Minor > Fix For: 7.0 > > > The display of binding property names in the Properties window is inconsistent. The name of the property is correct derived from the connector type property DisplayName when a binding is selected in the Connectors view. The name of the property is incorrectly derived from the connector types property Name when a connector type is selected in the Connectors view. > eg, Clicking on the SalesforceConnector type, shows a 'username' property in the Properties view. Clicking on an active Salesforce binding, shows a 'User Name' property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-424) New Connector UI (Dialog, Panel) Has Several Problems

by Dan Florian (JIRA)

New Connector UI (Dialog, Panel) Has Several Problems ----------------------------------------------------- Key: TEIIDDES-424 URL: https://jira.jboss.org/jira/browse/TEIIDDES-424 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 7.0 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.0 Here are 3 problems: (1) the new connector dialog and panel i8n is not working, (2) the correct connector type is not being selected when the dialog opens, and (3) the dialog message indicates the connector name is empty when it is not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-239) CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-239?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-239: ---------------------------------- Fix Version/s: 7.1 (was: 7.0) > CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-239 > URL: https://jira.jboss.org/browse/TEIIDDES-239 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 6.1.0, 6.2.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 7.1 > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-219) SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-219?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-219: ---------------------------------- Fix Version/s: 7.1 (was: 7.0) > SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-219 > URL: https://jira.jboss.org/browse/TEIIDDES-219 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Documentation, Import/Export > Affects Versions: 6.0.0 > Environment: Designer 5.5.3 MS1 build > Reporter: Greg Haber > Priority: Minor > Fix For: 7.1 > > > I noticed that as of MS1, the SFDC importer plugin contains a lot of copies of third party jars, most Apache Axis/Apache Commons stuff. In many cases, these same jars are also in the com.metamatrix.modeler.dqp_5.5.3 plugin since they are also needed by the SFDC connector. I also noticed that some of our other Designer plugins that use external jars put those jars in their own plugins, and import the plugin, rather than putting them in the same plugin as our own code. > We should consider pulling these jars out of the SFDC importer plugin and putting them in their own plugins (which the SFDC importer plugin can then import), or simply importing them in the SFDC importer plugin from the DQP plugin. > The same problem exists to a much lesser degree in the WSDL importer (just the commons-codec-1.2.jar is duplicated in that one). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-444) Exception saving VDB with non-relational models that have no "Data Source" name value

by Barry LaFond (JIRA)

Exception saving VDB with non-relational models that have no "Data Source" name value ------------------------------------------------------------------------------------- Key: TEIIDDES-444 URL: https://jira.jboss.org/browse/TEIIDDES-444 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Assignee: John Verhaeg Priority: Blocker Fix For: 7.0 1) Create VDB 2) Add Virtual Model that has one Source model dependency to VDB. This should result in an "Empty" Data source name since this is not a source model. 3) Save VDB and get following exception stating that the data source name is basically required. Caused by: javax.xml.bind.MarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'name' must appear on element 'source'.] at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317) at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75) at org.teiid.designer.vdb.Vdb$2.tryToDo(Vdb.java:372) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:37) ... 51 more Caused by: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'name' must appear on element 'source'. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-443) Model Description in VDB Editor from persisted VDB shows wrong description

by Barry LaFond (JIRA)

Model Description in VDB Editor from persisted VDB shows wrong description -------------------------------------------------------------------------- Key: TEIIDDES-443 URL: https://jira.jboss.org/browse/TEIIDDES-443 Project: Teiid Designer Issue Type: Bug Components: Editors, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Fix For: 7.0 1) Create VDB 2) Set VDB Description to "VDB Description" 3) Add Model 4) Set Description on model to "Model Description" and SAVE VDB 5) Close VDB Editor 6) Re-open VDB in VDB Editor 7) Notice that model description says "VDB Description" Note that the actual model description in vdb.xml file is correct, so the "Write" part works, just not the setting of the description column in the VDB Editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010