July 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-519) Delete project - Unhandled event loop exception and project not deleted

by Warren Gibson (JIRA)

Delete project - Unhandled event loop exception and project not deleted ----------------------------------------------------------------------- Key: TEIIDDES-519 URL: https://jira.jboss.org/browse/TEIIDDES-519 Project: Teiid Designer Issue Type: Bug Components: Housekeeping Affects Versions: 7.0 Reporter: Warren Gibson Running Teiid Designer in JBoss Developer Studio Imported BQT_ORCL9 project attached. Did some editing Decided to delete the project. Selected the project in the Model Expl tree with right mouse. Selected delete. Got a dialog wanting me to confirm the delete. Selected Yes for the delete. Project was not get deleted from tree. Refreshed the tree and project still exists. Notice an Unhandled event loop exception: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.SWT.error(SWT.java:3770) at org.eclipse.swt.widgets.Widget.error(Widget.java:450) at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:532) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:155) at org.eclipse.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) 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.executeCommandInContext(HandlerService.java:270) at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95) at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47) at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:481) at com.metamatrix.modeler.internal.ui.actions.DeleteResourceAction.doRun(DeleteResourceAction.java:386) 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.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: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

14 years, 1 month

2
1
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

14 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-491) Procedures with ERROR 'error message text' are interpreted as assignments and then fail as Element ""ERROR"" is not defined by any relevant group

by Paul Nittel (JIRA)

Procedures with ERROR 'error message text' are interpreted as assignments and then fail as Element ""ERROR"" is not defined by any relevant group ------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-491 URL: https://jira.jboss.org/browse/TEIIDDES-491 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer 6/28 Reporter: Paul Nittel I found this while testing Dynamic SQL where ERROR 'some message' is morphed into "ERROR" = 'some message' when the transformation SQL is validated. No way around it. Steve H. wonders if it's due to ERROR being inherited from assignment (or some such ;-). -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-482) Synchronizing models in a VDB does not work quite as expected

by Paul Nittel (JIRA)

Synchronizing models in a VDB does not work quite as expected ------------------------------------------------------------- Key: TEIIDDES-482 URL: https://jira.jboss.org/browse/TEIIDDES-482 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer from 6/28 Reporter: Paul Nittel Attachments: SynchronizeThis.zip Assuming I have a VDB which contains models, 1 - Modify one of the models 2 - Save the model 3 - The VDB editor shows the large "Synchronize All" button is enabled and the synch checkbox associated with the changed model is an empty checkbox. (The other checkboxes are large gray squares.) 4 - Click the checkbox (it now turns into the gray square - the large "All" button remains enabled) 5 - Save the VDB Now the large "Synchronize All" button is disabled If I click the "Synchronize All" button first, the checkbox is affected and the large button remains enabled until the VDB is saved. (If I click it again, it still goes through the synch process.) I would expect the button and checkbox(es) to work together and that once all models are synched, the large button would be disabled even without the VDB being saved. (Oddly, once I save a model in the VDB, the VDB becomes dirty. Maybe this is intentional, but now I don't have the option to deploy that VDB until I synch it.) -- 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

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-511) Designer "Help About" lists Teiid's provider as "Red Hat, Inc." - Should be "JBoss by Red Hat" like the others

by Paul Nittel (JIRA)

Designer "Help About" lists Teiid's provider as "Red Hat, Inc." - Should be "JBoss by Red Hat" like the others -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-511 URL: https://jira.jboss.org/browse/TEIIDDES-511 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Environment: All Reporter: Paul Nittel Selecting the Teiid icon at the bottom of Help About JBoss Developer Studio brings up the Teiid features. "Red Hat, Inc." is listed as provider. For all other JBoss features, the provider is "JBoss by Red Hat". Please change so Teiid matches its sibling features. (Check the copyright information, too, please.) -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-523) Add WS-Security (UsernameToken) Support to Generated JBossWS-CXF War

by Ted Jones (JIRA)

Add WS-Security (UsernameToken) Support to Generated JBossWS-CXF War -------------------------------------------------------------------- Key: TEIIDDES-523 URL: https://jira.jboss.org/browse/TEIIDDES-523 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones -- 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

14 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-507) Teiid 7.0 Designer does not display XML results - Instead get "org.teiid.core.types.SQLXMLImpl@8f2d5e"

by Paul Nittel (JIRA)

Teiid 7.0 Designer does not display XML results - Instead get "org.teiid.core.types.SQLXMLImpl@8f2d5e" ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-507 URL: https://jira.jboss.org/browse/TEIIDDES-507 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final Reporter: Paul Nittel I have created a simple XML document model (bookListing). After deploying the VDB to a Teiid server, executing a query ("select * from booksDoc.bookListingDocument") produces this cryptic result: org.teiid.core.types.SQLXMLImpl@8f2d5e. It should display the actual XML output, preferably formatted in the tree format. There do not appear to be any related exceptions when I execute the query. Model project set shall be attached! -- 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

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-522) Recursive XML doc model does not create mapping class structure for lower levels

by Paul Nittel (JIRA)

Recursive XML doc model does not create mapping class structure for lower levels -------------------------------------------------------------------------------- Key: TEIIDDES-522 URL: https://jira.jboss.org/browse/TEIIDDES-522 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid 7 Designer Reporter: Paul Nittel I am following the E2eRecursiveXmlTextSource test script. I create a document model, based on the imported XSD and step through the creation wizard. On the third page, per the instructions, I expand the tree and select (check) the Supervisor node before clicking finish. What I get is a Supervisor mapping class which has no mapping tree elements against which to link the columns (which I add manually, again, per the instructions). It is possible this represents new behavior, but I suspect not. I'm attaching the Model Project Set (which has 3 projects). -- 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

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-525) In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props).

by Ken Johnson (JIRA)

In Import wizards, add ability to launch Connection Profile property editor (so I can easily fix bad connection props). ----------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-525 URL: https://jira.jboss.org/browse/TEIIDDES-525 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.0 Environment: Teiid Designer 7, Helios, RHEL 6, OpenJDK 6 Reporter: Ken Johnson When importing (e.g. Metadata from JDBC Database), I can choose an existing connection profile or create a new one. If the one I create or choose has an error - say a bad password, to fix it I have to: 1. cancel out of the import wizard 2. switch perspectives to DTP 3. edit the properties for the offending connection profile 4. switch perspective back to Designer 5. re-run import wizard to try again. Since connection property errors are a common occurrence, this is a usability issue. Suggest adding the ability to launch the connection profile property editor directly from the import wizard so the correction can be made, saved, and retested without the context switches. -- 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

14 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-481) Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked

by Paul Nittel (JIRA)

Checkboxes in VDB editor for Synch and visibility are "unusual" and never checked --------------------------------------------------------------------------------- Key: TEIIDDES-481 URL: https://jira.jboss.org/browse/TEIIDDES-481 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Milestone build from 6/28 Reporter: Paul Nittel Assuming I have a VDB which contains models, 1 - Modify one of the models 2 - Save the model 3 - The VDB editor shows the large "Synchronize All" button is enabled and the synch checkbox associated with the changed model is an empty checkbox. (The other checkboxes are large gray squares. See attached screenshot.) 4 - Click the checkbox (it now turns into the gray square - the large "All" button remains enabled) 5 - Save the VDB Now the large "Synchronize All" button is disabled If I click the "Synchronize All" button first, the checkbox is affected and the large button remains enabled until the VDB is saved. I would expect the button and checkbox(es) to work together and that once all models are synched, the large button would be disabled even without the VDB being saved. (Oddly, once I save a model in the VDB, the VDB becomes dirty. Maybe this is intentional, but now I don't have the option to deploy that VDB until I synch it.) -- 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

14 years, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010