April 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1498) TEIID31100 Parsing error: : Encountered "(" at line 1, column 6.

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1498?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1498. --------------------------------- Resolution: Partially Completed Marking as partially fixed until backported > TEIID31100 Parsing error: : Encountered "(" at line 1, column 6. > ---------------------------------------------------------------- > > Key: TEIIDDES-1498 > URL: https://issues.jboss.org/browse/TEIIDDES-1498 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.7 > Environment: Windows + JBoss 7.1.1. + TEIID 8.1 + Designer 7.8 (not available in combo) > Reporter: luca gioppo > Assignee: Ted Jones > Fix For: 7.7.3, 8.1 > > > As for forum reference: > https://community.jboss.org/thread/205730?start=0&tstart=0 > I seems that Designer is not able to create web service operations without parameters and in the end the war is "not building the query correctly when there are no parameters". > Francly I did not understand who does the error (the web service wizard from the physical model or the cxf wizard from the VBD). > The result is that if there are no parameters in the soap call there is an error -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1647) Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1647?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1647: -------------------------------- Fix Version/s: 8.2 (was: 8.1) > Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1647 > URL: https://issues.jboss.org/browse/TEIIDDES-1647 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > Attachments: WSDL XSDs Imported.zip > > > Ex: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT > XMLELEMENT(NAME "soap:Envelope", XMLNAMESPACES('http://schemas.xmlsoap.org/soap/envelope/' AS soap, DEFAULT 'http://otda.ny.gov/intake/caseinqwsdl/1_0', DEFAULT 'http://otda.ny.gov/intake/caseinquiryin/1_0'), XMLELEMENT(NAME "soap:Header"), XMLELEMENT(NAME "soap:Body", XMLELEMENT(NAME CaseInquiry, XMLELEMENT(NAME CaseNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.CaseNumber), XMLELEMENT(NAME DistrictNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.DistrictNumber)))) AS > xml_out; > END > > ERROR: At most only one NO DEFAULT or DEFAULT namespace may be specified. > -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1647) Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1647?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1647: ------------------------------------- Moving to 8.2 > Multiple NODEFAULT and DEFAULT NS Added to Generated Procedure When Importing WSDL > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1647 > URL: https://issues.jboss.org/browse/TEIIDDES-1647 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > Attachments: WSDL XSDs Imported.zip > > > Ex: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT > XMLELEMENT(NAME "soap:Envelope", XMLNAMESPACES('http://schemas.xmlsoap.org/soap/envelope/' AS soap, DEFAULT 'http://otda.ny.gov/intake/caseinqwsdl/1_0', DEFAULT 'http://otda.ny.gov/intake/caseinquiryin/1_0'), XMLELEMENT(NAME "soap:Header"), XMLELEMENT(NAME "soap:Body", XMLELEMENT(NAME CaseInquiry, XMLELEMENT(NAME CaseNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.CaseNumber), XMLELEMENT(NAME DistrictNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.DistrictNumber)))) AS > xml_out; > END > > ERROR: At most only one NO DEFAULT or DEFAULT namespace may be specified. > -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1641: -------------------------------- Fix Version/s: 8.2 (was: 8.1) > Eclipse Juno 4.0 freezes while generating JBossWS-CXF war > --------------------------------------------------------- > > Key: TEIIDDES-1641 > URL: https://issues.jboss.org/browse/TEIIDDES-1641 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.8 > Environment: fedora 17, x86_64, > eclipse juno 4.0, sr1 > teiid designer 8.1.alpha2 (also 7.8) > Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1 > server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1 > java jdk 1.6.0_33 > Reporter: Lucie Fabrikova > Assignee: Ted Jones > Fix For: 8.2 > > Attachments: WebServ.zip > > > !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278 > !MESSAGE An error occurred while creating WAR file, check log for detail > !STACK 0 > java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>". > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718) > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171) > at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116) > 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$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > 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:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > 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:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1641) Eclipse Juno 4.0 freezes while generating JBossWS-CXF war

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1641?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1641: ------------------------------------- Moving to 8.2 pending re-testing > Eclipse Juno 4.0 freezes while generating JBossWS-CXF war > --------------------------------------------------------- > > Key: TEIIDDES-1641 > URL: https://issues.jboss.org/browse/TEIIDDES-1641 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.8 > Environment: fedora 17, x86_64, > eclipse juno 4.0, sr1 > teiid designer 8.1.alpha2 (also 7.8) > Abridged JBoss Tools 4.0 -> JBossAS Tools 2.4.1 > server: SOA 5.3.1.GA + eds 5.3.1.GA or JBossAS 7.1.1 > java jdk 1.6.0_33 > Reporter: Lucie Fabrikova > Assignee: Ted Jones > Fix For: 8.2 > > Attachments: WebServ.zip > > > !ENTRY org.teiid.designer.webservice 4 5 2013-04-08 10:36:50.278 > !MESSAGE An error occurred while creating WAR file, check log for detail > !STACK 0 > java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>". > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718) > at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159) > at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171) > at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116) > 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$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > 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:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > 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:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1633) XML Namespaces are not imported for Child Element

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1633?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1633: ----------------------------------- Fix Version/s: 7.7.3 (was: 7.8) > XML Namespaces are not imported for Child Element > ------------------------------------------------- > > Key: TEIIDDES-1633 > URL: https://issues.jboss.org/browse/TEIIDDES-1633 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.6 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 7.7.3, 8.2 > > > XML Namespaces are not imported for Child Elements while creating XML Document model. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1665) Dialog Title for 'Create User Defined Function' is wrong.

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1665?page=com.atlassian.jira.plu... ] Dan Florian resolved TEIIDDES-1665. ----------------------------------- Resolution: Done PR merged into master branch. > Dialog Title for 'Create User Defined Function' is wrong. > --------------------------------------------------------- > > Key: TEIIDDES-1665 > URL: https://issues.jboss.org/browse/TEIIDDES-1665 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Dan Florian > Fix For: 8.1 > > > The dialog title when creating a User Defined Function is wrong. > 1) In Model Explorer, select a relational view model > 2) Rt Click > New Child > Procedure... > 3) On the Select Procedure Type dialog, choose 'User Defined Function', the click OK. > 4) The title of the main dialog is "Create Relational View Table User Defined Function" > The word 'Table' should be removed - even better, shorten it to "Create User Defined Function" -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1666) Error creating Udf in a view Model via the Create Child Procedure dialog

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1666?page=com.atlassian.jira.plu... ] Dan Florian resolved TEIIDDES-1666. ----------------------------------- Resolution: Done PR merged into master branch. > Error creating Udf in a view Model via the Create Child Procedure dialog > ------------------------------------------------------------------------ > > Key: TEIIDDES-1666 > URL: https://issues.jboss.org/browse/TEIIDDES-1666 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Dan Florian > Fix For: 8.1 > > Attachments: CreateUdfInViewExceptions.txt > > > When using the New Child > Procedure... Dialog to create a UDF within a VIEW Model, the UDF properties are not getting set and generated procedure has errors. See attached exception from designer log. > Note that this same process in a Source Model *does* work ok. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1560) Add Support for Query Parameters in Generated REST War

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1560?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1560: --------------------------------------- Lucie, Did you get your answer or is this still an issue? > Add Support for Query Parameters in Generated REST War > ------------------------------------------------------ > > Key: TEIIDDES-1560 > URL: https://issues.jboss.org/browse/TEIIDDES-1560 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.8, 8.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.7.2, 8.1 > > > The generated REST war supports path parameters and XML/JSON inputs, but does not allow for query parameters. We should support query parameters as well. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1633) XML Namespaces are not imported for Child Element

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1633?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1633: ---------------------------------- Fix Version/s: 7.8 > XML Namespaces are not imported for Child Element > ------------------------------------------------- > > Key: TEIIDDES-1633 > URL: https://issues.jboss.org/browse/TEIIDDES-1633 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.6 > Reporter: Van Halbert > Assignee: Ted Jones > Fix For: 7.8, 8.2 > > > XML Namespaces are not imported for Child Elements while creating XML Document model. -- 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2013