October 2010 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-313) Recursion limit "spinner" does not work

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-313?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-313: ---------------------------------- Attachment: Employees.xsd XML Schema was recursive element > Recursion limit "spinner" does not work > --------------------------------------- > > Key: TEIIDDES-313 > URL: https://jira.jboss.org/browse/TEIIDDES-313 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.0, 7.1, 7.1.1 > Environment: Fedora 10, 5.5SP4 build 3191 > Reporter: Paul Nittel > Assignee: Dan Florian > Fix For: 7.1.1 > > Attachments: Employees.xsd, RecursiveText.zip > > > Running the E2E Recursive Text Source employees test, the spinner control used to limit recursion levels does not respond to clicking the up & down arrows. I'm attaching a model project set containing the project. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-313) Recursion limit "spinner" does not work

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-313?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-313: ---------------------------------- Assignee: Dan Florian (was: Barry LaFond) Fix Version/s: 7.1.1 Affects Version/s: 7.0 7.1.1 Priority: Major (was: Minor) > Recursion limit "spinner" does not work > --------------------------------------- > > Key: TEIIDDES-313 > URL: https://jira.jboss.org/browse/TEIIDDES-313 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.0, 7.1, 7.1.1 > Environment: Fedora 10, 5.5SP4 build 3191 > Reporter: Paul Nittel > Assignee: Dan Florian > Fix For: 7.1.1 > > Attachments: RecursiveText.zip > > > Running the E2E Recursive Text Source employees test, the spinner control used to limit recursion levels does not respond to clicking the up & down arrows. I'm attaching a model project set containing the project. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-285) Designer install into folder containing spaces results in VDB creation errors

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-285?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-285. ----------------------------------- Resolution: Cannot Reproduce Bug This issue has been worked and fixed in Teiid Designer 7.0, 7.1 + and includes a new VDB editing framework. > Designer install into folder containing spaces results in VDB creation errors > ------------------------------------------------------------------------------ > > Key: TEIIDDES-285 > URL: https://jira.jboss.org/browse/TEIIDDES-285 > Project: Teiid Designer > Issue Type: Bug > Environment: Windows > Reporter: Mark Drilling > Assignee: Barry LaFond > > This Issue has been encountered multiple times. > If the Designer is installed in a directory that contains spaces in its name, we are unable to build/save a VDB. > For example, if the Designer is installed in C:\Program Files\MetaMatrix\EnterpriseDesigner and we create a new VDB and add models to it, everything appears fine. When we perform a Save, we see an error indicated on the VDB Overview page. > ERROR - This VDB cannot be deployed for data access > On the VDB Problems page we see an error message: > Missing model import to resource ../../../../../../../../../../../Program%2520Files/MetaMatrix/EnterpriseDesigner/workspace/.metadata/.plugins/com.metamatrix.vdb.edit/vdbWorkingFolder/1174623145637_392809865332324117/builtInDataTypes.xsd > No log file is produced and no errors seem to be logged to Designer's Problems view. > It appears the space in the referenced file name may not be encoded properlly. The URL encoded value used is %2520. I think it should be %20 (decimal 32) however this may be wchar or UTF-8. In either case, the space is the cause of the issue. If I rename the Program Files directory to ProgramFiles, all is fine. (i.e. C:\ProgramFiles\MetaMatrix\EnterpriseDesigner. > The use case for the client suggests that the client toosl should be installed according to standard business logic and placed in a common location. This common location may contain spaces in the path name. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-272) Allow query plans to be viewed within Designer without requiring that all bindings start successfully

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-272?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-272. ----------------------------------- Resolution: Won't Fix VDB framework totally changed. Connection framework totally changed. This JIRA is irrelevant with Teiid Designer 7.0 + > Allow query plans to be viewed within Designer without requiring that all bindings start successfully > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-272 > URL: https://jira.jboss.org/browse/TEIIDDES-272 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Michael Walker > Assignee: Barry LaFond > > Developers want to view query plans when designing their models. Unfortunately, there is no way to view the query plan without executing a VDB. Fortunately, VDBs can be executed within Designer, so the query plans can be viewed within SQLExplorer. > However, if any connector binding fails to start for a given VDB running in Designer, then no query plans can be generated. Even if you use "OPTION PLANONLY", you will receive the error "connector binding X failed to start" and no plan will be generated. > Query plans are valuable at design time, but we've required a runtime environment be fully available in order to view them. We should allow users to view query plans from within Designer, even when bindings fail to start, so long as "OPTION DEBUG" is used. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-198) Error in TestServerRuntimeMetadata unit test

by Barry LaFond (JIRA)

Error in TestServerRuntimeMetadata unit test -------------------------------------------- Key: TEIIDDES-198 URL: https://jira.jboss.org/jira/browse/TEIIDDES-198 Project: Teiid Designer Issue Type: Bug Reporter: Barry LaFond Fix For: 6.1.1 Error in TestServerRuntimeMetadata.testGetXmlSchemas() method. Appears that the TreeMappingRootSqlAspect.getTransformationInfo() method is calling toUpperCase() on the Import locations. This results in an XSD file potentially having Case Sensitivity problems on LINUX, in this case. Need to investigate removing this toUpperCase() call. This has not manifested itself because it's a runtime/server thing and only happens if the XML validation is turned on which is basically not done. Our unit test happens to test ALL the basic methods and we haven't run unit tests consistently on LINUX until recently with Teiid Designer. -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-281) Import WSDL as Web Svc allows viewing of WSDL, but there is no file association

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-281?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-281. ----------------------------------- Resolution: Won't Fix Eclipse, and the "wst" project specifically, treats WSDL files different than Text files. Preferences > Editors > File Associations framework doesn't work. Click on Preferences > Content Types to see WSDL Files option. Will not address with Designer since it's not a Designer-specific area. > Import WSDL as Web Svc allows viewing of WSDL, but there is no file association > ------------------------------------------------------------------------------- > > Key: TEIIDDES-281 > URL: https://jira.jboss.org/browse/TEIIDDES-281 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 7.1 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > > I was importing the Amazon WSDL file - http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl - and found it had an error. I right-clicked the file in the imported to view the WSDL, but there was no editor associated with that file. I went to Windows > Preferences to add the association, but WSDL is not a known file type. > I think we need to add .wsdl and associate an 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-79) Description info in source model not copied to view when built via transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-79?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved TEIIDDES-79. ---------------------------------- Resolution: Done Tested with Teiid Designer 7.1.x kit, 10/21/2010. Created descriptions for Model, Table & Column With "Copy Descriptions" == TRUE, the descriptions were copied. With "Copy Descriptions" == FALSE, the Table & Column descriptions were NOT copied, but the description for the Model was copied. > Description info in source model not copied to view when built via transformation > --------------------------------------------------------------------------------- > > Key: TEIIDDES-79 > URL: https://jira.jboss.org/browse/TEIIDDES-79 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > I imported Books from a relational source and added a few descriptions to some columns. I then created a new relational view model, using the optional builder to transform from an existing model. All metadata was copied correctly EXCEPT the descriptions. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-158) Failing to check Allow Updates in Designer generates unexpected errors

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-158?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-158. ----------------------------------- Resolution: Won't Fix This is old pre-7.0 Designer VDB framework which has no notion of a "Allow Updates" option. > Failing to check Allow Updates in Designer generates unexpected errors > ---------------------------------------------------------------------- > > Key: TEIIDDES-158 > URL: https://jira.jboss.org/browse/TEIIDDES-158 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Designer running on Windows > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > Attachments: ModelProjectSet_45.zip, XaExceptionDesigner2.log > > > My goal was to execute the Updateable Web Service queries from the Designer, now that we have that capability. > I created the VDB, forgot to check the Allow All Updates box, and tried to Insert a new Product. This failed. I returned to the VDB Execution page in the Model Explorer, checked the box, and re-executed the VDB. At this point, it gets an error while preparing (not sure if it was reading metadata or what). > I exited and restarted the Designer, checked the box appropriately, and was able to test. (It worked.) > While Ramesh watched, I tried to reproduce and was successful. We thought disconnecting before re-executing the VDb would help, but it did not. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-661) Update list of DDL dialects on Export DDL dialog to reflect current DB versions

by Ken Johnson (JIRA)

Update list of DDL dialects on Export DDL dialog to reflect current DB versions ------------------------------------------------------------------------------- Key: TEIIDDES-661 URL: https://jira.jboss.org/browse/TEIIDDES-661 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Environment: JBDS 4 Beta 1, RHEL 6 Reporter: Ken Johnson Fix For: 7.1.1 When exporting DDL, the Types of DDL listed in the drop list on the Export DDL dialog reflect very old DB versions. The supported DBs should be: IBM DB2 (specifically v9.7) Oracle (specifically 10/11g) MS SQL Server (specifically v2008) MySQL (specifically v 5.0/5.1) PostgreSQL (specifically v8.3/8.4) -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-665) Find Model Object does nothing on first attempt, then gets Unhandled event loop exception

by Paul Nittel (JIRA)

Find Model Object does nothing on first attempt, then gets Unhandled event loop exception ----------------------------------------------------------------------------------------- Key: TEIIDDES-665 URL: https://jira.jboss.org/browse/TEIIDDES-665 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Environment: JBDS 4.0.0 M2 and Beta 1 (I tried both) Reporter: Paul Nittel Fix For: 7.1.1 With a model project open, start the Find Model Object tool (Search > Teiid Designer > Find Model Object). Choose an object to find (like a column in a table) from the list of Matching Model Object list. When the Locations list is populated, click OK. The first time nothing apparent happens. Subsequent tries result in the following exception: Error 2010-10-19 10:21:30.380 Unhandled event loop exception java.lang.NullPointerException at com.metamatrix.modeler.internal.ui.actions.FindModelObjectHandler.execute(FindModelObjectHandler.java:45) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) 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: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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- 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, 6 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 October 2010