February 2011 - teiid-designer-issues

[JBoss JIRA] Resolved: (TEIIDDES-852) Teiid VDB editor throws "Unhandled event loop exception" when in place description editing started in other files list

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-852?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-852. ----------------------------------- Resolution: Done added NULL check for description in VdbEntry constructor. Setting to empty string "" if null. > Teiid VDB editor throws "Unhandled event loop exception" when in place description editing started in other files list > ---------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-852 > URL: https://issues.jboss.org/browse/TEIIDDES-852 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.2 > Reporter: Denis Golovin > Assignee: Barry LaFond > Fix For: 7.3 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-854) Create Web Service Action should request to save modified editor before wizard wizard is shown

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-854?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-854: ---------------------------------- Fix Version/s: 8.0 Priority: Minor (was: Major) > Create Web Service Action should request to save modified editor before wizard wizard is shown > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-854 > URL: https://issues.jboss.org/browse/TEIIDDES-854 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.2 > Reporter: Denis Golovin > Assignee: Barry LaFond > Priority: Minor > Labels: usability > Fix For: 8.0 > > Attachments: screenshot82.png, screenshot83.png > > > Now on new unsaved diagram with changes Create Web Service Wizard reports error and the only choice is close it, save diagram and then start wizard again. > Error text is: "All models must be saved and validated prior to generation" for modified diagram, > !screenshot82.png! > but it lets create Web Service without any errors on unmodified diagram, when there are saved and unsaved models in project. > !screenshot83.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-858) Cannot Print Metadata Model Diagram under Linix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-858?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-858: ---------------------------------- Fix Version/s: 8.0 Designer's Diagram print capabilities were built on "hacking" OS-type code. Not sure about this. We had Large Diagram print problems before. Basically a "no more handles" size OS Display problem. Maybe we should yank this capability. (with it "Show Grid" actions too??) > Cannot Print Metadata Model Diagram under Linix > ----------------------------------------------- > > Key: TEIIDDES-858 > URL: https://issues.jboss.org/browse/TEIIDDES-858 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dialogs > Affects Versions: 7.1 > Environment: Arch: Linux,GTK,x86 > Distr: Ubuntu 10.10 > Reporter: Denis Golovin > Assignee: Steven Hawkins > Fix For: 8.0 > > > After creating diagram Select File->Print from bar menu. Then select printer and press Print button. It shows error dialog and reports exception in Error Log View: > {noformat}org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4109) > at org.eclipse.swt.SWT.error(SWT.java:3998) > at org.eclipse.swt.SWT.error(SWT.java:3969) > at org.eclipse.swt.printing.Printer.internal_new_GC(Printer.java:393) > at org.eclipse.swt.graphics.GC.<init>(GC.java:159) > at org.eclipse.swt.graphics.GC.<init>(GC.java:125) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getPrinterGC(DiagramPrintingAnalyzer.java:228) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getFreshPrinterGraphics(DiagramPrintingAnalyzer.java:220) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printLandscape_PrinterIsPortrait(DiagramPrintingOperation.java:690) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printPages(DiagramPrintingOperation.java:403) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.countPages(DiagramPrintingAnalyzer.java:170) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.setPageSize(DiagramPrintingAnalyzer.java:68) > at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.<init>(DiagramPrintingAnalyzer.java:44) > at com.metamatrix.modeler.diagram.ui.actions.PrintWrapper.doRun(PrintWrapper.java:100) > at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) > at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) > at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:820) > at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:806) > at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:796) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) > 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: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:619) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) > at org.eclipse.equinox.launcher.Main.run(Main.java:1407){noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-637) Create a Recorded Demo for the Waar Generation Process

by Ted Jones (JIRA)

Create a Recorded Demo for the Waar Generation Process ------------------------------------------------------ Key: TEIIDDES-637 URL: https://jira.jboss.org/browse/TEIIDDES-637 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to blog about the new War Generation feature and create a recorded demo -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-839) SOAPAction in Generated WSDL Should be Removed

by Ted Jones (JIRA)

SOAPAction in Generated WSDL Should be Removed ---------------------------------------------- Key: TEIIDDES-839 URL: https://issues.jboss.org/browse/TEIIDDES-839 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.2 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.3 The generated WSDL for Web Service models contains a SOAPAction value that was used for legacy web services in MMX. Ir causes issues with a SOAPProxy deployed to ESB/SOA-P. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-701) Create Document to assist users in migrating legacy Metamatrix artifacts to Teiid artifacts

by Barry LaFond (JIRA)

Create Document to assist users in migrating legacy Metamatrix artifacts to Teiid artifacts ------------------------------------------------------------------------------------------- Key: TEIIDDES-701 URL: https://jira.jboss.org/browse/TEIIDDES-701 Project: Teiid Designer Issue Type: Task Reporter: Barry LaFond TEIIDDES-684 was logged to insure that users of Metamatrix product had a migration path to insure that legacy artifacts and the metadata they contain will be transportable and usable in the Teiid & Teiid Designer framework. This Task will involve creating a document which describes the differences between frameworks and provides a step-by-step process to migrate Model Projects, Models and potentially VDB's into Teiid & Teiid Designer 7.X capabilities. -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-816) Refactor Common Code Between TeiidAdminInfo And TeiidJdbcInfo Into A Superclass

by Dan Florian (JIRA)

Refactor Common Code Between TeiidAdminInfo And TeiidJdbcInfo Into A Superclass ------------------------------------------------------------------------------- Key: TEIIDDES-816 URL: https://issues.jboss.org/browse/TEIIDDES-816 Project: Teiid Designer Issue Type: Task Affects Versions: 7.2 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.3 95% of the code in TeiidAdminInfo And TeiidJdbcInfo is exactly the same. They share all the same fields except one. Refactoring the common code into an abstract base class would be a better design. Also, the "host" field should really be a property of a Server. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-345) More accurate importing of JDBC numeric types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-345?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDDES-345: ----------------------------------------- This has been addressed by importing changes in 7.1 the importer will no longer try so hard to infer the use of a more specific type than what is suggested by the jdbc sql type code. > More accurate importing of JDBC numeric types > --------------------------------------------- > > Key: TEIIDDES-345 > URL: https://issues.jboss.org/browse/TEIIDDES-345 > Project: Teiid Designer > Issue Type: Bug > Reporter: Marc Shirley > > sometimes we import fixed precision source types as floats and vice versa -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-822) Fully-qualified names should not be required when referencing procedures that have unique unqualified names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-822?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIIDDES-822. ------------------------------------- Resolution: Done looks good to me. fully and partially qualified work, and ambiguity is detected (although it could be worded a little better). > Fully-qualified names should not be required when referencing procedures that have unique unqualified names > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-822 > URL: https://issues.jboss.org/browse/TEIIDDES-822 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.0 > Reporter: Michael Walker > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.3 > > Attachments: TransformationMetadata.java.patch > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-860) CLONE - Preview data failing for example project.

by Barry LaFond (JIRA)

CLONE - Preview data failing for example project. ------------------------------------------------- Key: TEIIDDES-860 URL: https://issues.jboss.org/browse/TEIIDDES-860 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.3 Import Parts Example project Continue with example and try to preview or Execute VDB and get no "Source" error from Teiid. Problem is the Preview VDB is being created prior to the PartsSourceA.xmi being fully loaded. Result is the ModelEntry for it contains ModelType == "Type" instead of "Physical". Fix is to not respond to Open Project events in TEiid Designer "PreviewManager" class -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 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 February 2011