March 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-112) Function Model Diagram Object Positions Can't Be Persisted

by Dan Florian (JIRA)

Function Model Diagram Object Positions Can't Be Persisted ---------------------------------------------------------- Key: TEIIDDES-112 URL: https://jira.jboss.org/jira/browse/TEIIDDES-112 Project: Teiid Designer Issue Type: Bug Components: Diagrams Affects Versions: 6.0 Reporter: Dan Florian With the FunctionDefinitions.xmi Model Editor open, import a UDF zip file. After the import, move some of the diagram objects around and Save. Notice that the diagram obects positions change back to their original positions. It is impossible to persist changes in diagram object positions. Barry L. mentioned that this sounds like a problem in diagram object caching. -- 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
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-117) JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime.

by Ken Johnson (JIRA)

JDBC driver JARs added when creating a new JDBC source at import time should be added as extension JARs so the connector works at runtime. ------------------------------------------------------------------------------------------------------------------------------------------ Key: TEIIDDES-117 URL: https://jira.jboss.org/jira/browse/TEIIDDES-117 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 6.0.0 Environment: Ganymede 3.4.1 JEE environment + Teiid Designer 6.0.0 pre-release. Reporter: Ken Johnson Given that Designer does not bundle any JDBC driver JARs, the need to be added by the user. Currently they are required in two places: 1. when defining an import source 2. for the connector used during preview and testing (extension jar) The user has to deal with importing the driver JARs in two different ways to support the logical operation of Import->Model->Preview. Suggest: a) providing a single new mechanism for adding driver JARs to the tooling so they are available for both Import and Preview/Execution, or b) automatically add extension JAR for Preview/Execution when specifying driver JAR during import source configuration, or c) both In the present implementation, a novice user will have a heck of a time understanding why Preview doesn't work when they just added the JAR while configuring the source for import. -- 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
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-118) Preview Data View History SQL Tooltip Does Not Update

by Dan Florian (JIRA)

Preview Data View History SQL Tooltip Does Not Update ----------------------------------------------------- Key: TEIIDDES-118 URL: https://jira.jboss.org/jira/browse/TEIIDDES-118 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 6.0.0 Reporter: Dan Florian Assignee: Dan Florian Fix For: 6.0.0 Running a preview on a table that already has preview results displayed in the Preview Data View replaces the current results and does not create another entry in the view. However the tooltip that is displayed in the History list of the Preview Data View does not update to the latest SQL used to preview. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-120) Need ClassPath property editor for Connector Binding.

by Barry LaFond (JIRA)

Need ClassPath property editor for Connector Binding. ----------------------------------------------------- Key: TEIIDDES-120 URL: https://jira.jboss.org/jira/browse/TEIIDDES-120 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 6.0.0 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 6.0.0 Users need ability to change the class path of a connector binding (i.e. add/remove jars) by selecting jars on the file system as well as editing the text (for jars yet to be added??) The act of selecting a file system jar will COPY that jar to the .metamata's "extensions" folder for DQP use. This solves the problem of having to use the UDF view's import jar action to do the work for the connectors 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

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-124) Last page of WSDL File into Web Service model importer contains multiple invalid default values

by Barry LaFond (JIRA)

Last page of WSDL File into Web Service model importer contains multiple invalid default values ----------------------------------------------------------------------------------------------- Key: TEIIDDES-124 URL: https://jira.jboss.org/jira/browse/TEIIDDES-124 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Critical Fix For: 6.0.0 When you reach the last page of the wizard, the "Location" field is a just a "/" even though user had pre-selected a project when wizard was launched. Also, the generated "Model Name" contains the project name (i.e. BabelProject/BabelWSResponses). It should only contain the Model name. -- 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

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-127) Trying to export DDL gets NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin

by Paul Nittel (JIRA)

Trying to export DDL gets NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin ------------------------------------------------------------------------------------ Key: TEIIDDES-127 URL: https://jira.jboss.org/jira/browse/TEIIDDES-127 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Fedora 10, teiid_designer_TEST_032409 Reporter: Paul Nittel I created a small relational source model and tried to export it as DDL. I received this exception: Error 2009-03-24 15:25:02.01 Unhandled event loop exception java.lang.NoClassDefFoundError: com/metamatrix/modeler/ddl/DdlPlugin at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard.init(ExportDdlWizard.java:220) at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode.getWizard(WorkbenchWizardNode.java:185) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:104) at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSelectionPage.java:100) at org.eclipse.ui.internal.dialogs.ImportExportPage.getNextPage(ImportExportPage.java:431) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:97) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) 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:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171) at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:116) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) 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:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.teiid.designer.ddl (247). at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 53 more Caused by: org.osgi.framework.BundleException: The activator com.metamatrix.modeler.ddl.DdlPlugin for bundle org.teiid.designer.ddl is invalid at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:146) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:980) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111) ... 63 more Caused by: java.lang.NoClassDefFoundError: com/metamatrix/core/xslt/Style at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141) ... 68 more Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle org.teiid.designer.core.xslt (246). at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:125) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 74 more Caused by: org.osgi.framework.BundleException: The activator com.metamatrix.core.xslt.CoreXsltPlugin for bundle org.teiid.designer.core.xslt is invalid at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:146) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:980) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111) ... 84 more Caused by: java.lang.ClassCastException: com.metamatrix.core.xslt.CoreXsltPlugin cannot be cast to org.osgi.framework.BundleActivator at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:141) ... 89 more -- 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
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-125) WSDL to Relational Importer is putting %20 in path when importing from the filesystem on Linux.

by John Doyle (JIRA)

WSDL to Relational Importer is putting %20 in path when importing from the filesystem on Linux. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-125 URL: https://jira.jboss.org/jira/browse/TEIIDDES-125 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Linux OS Reporter: John Doyle Assignee: John Doyle Fix For: 6.0.0 If you import a WSDL from the filesystem and there is spaces in the path, %20 ends up in the path and the WSDL cannot be found by the validator. -- 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
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-128) Entering descriptions for bindings is not supported and generates excessive exceptions (1/character typed)

by Paul Nittel (JIRA)

Entering descriptions for bindings is not supported and generates excessive exceptions (1/character typed) ---------------------------------------------------------------------------------------------------------- Key: TEIIDDES-128 URL: https://jira.jboss.org/jira/browse/TEIIDDES-128 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Environment: fedora 10, 3/25/09 test version Reporter: Paul Nittel While working with connector bindings, I was able to get the description text field ENABLED and so entered a description. For each character I entered, I received an exception, part of which is shown below. If the field is DISABLED, you still get the exceptions. java.util.MissingResourceException: Can't find bundle for base name org.teiid.designer.ui.common.i18n, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1539) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1278) at java.util.ResourceBundle.getBundle(ResourceBundle.java:733) at com.metamatrix.ui.text.StyledTextEditor$ContextMenuAction.getFindAction(StyledTextEditor.java:927) at com.metamatrix.ui.text.StyledTextEditor$ContextMenuAction.isFindEnabled(StyledTextEditor.java:938) at com.metamatrix.ui.text.StyledTextEditor$ContextMenuAction.setEnabledState(StyledTextEditor.java:988) at com.metamatrix.ui.text.StyledTextEditor.getAction(StyledTextEditor.java:410) at com.metamatrix.ui.text.StyledTextEditor.keyReleased(StyledTextEditor.java:635) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:162) -- 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] Created: (TEIIDDES-123) WSDL to Web Service importer fails to create models

by Barry LaFond (JIRA)

WSDL to Web Service importer fails to create models --------------------------------------------------- Key: TEIIDDES-123 URL: https://jira.jboss.org/jira/browse/TEIIDDES-123 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Blocker Fix For: 6.0.0 1) Import "WSDL File into Web Service Model" 2) Select WSDL on file system (See attached example) 3) Specify model names when required 4) on last page, select "location" and valid model name (another bug with auto-named model name) 5) Select FINISH No models created. -- 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

16 years, 7 months

1
4
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-91) Designer - Deleting a project does not clean up all editors associated with that project.

by Dan Florian (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-91?page=com.atlassian.jira.pl... ] Dan Florian resolved TEIIDDES-91. --------------------------------- Resolution: Done Fixed the problem in SQLExplorer SQLEditor. This class is now a IResourceChangeListener. If the VDB or the IProject where the VDB is contained in is deleted this editor now closes. Reviewed by Barry L. > Designer - Deleting a project does not clean up all editors associated with that project. > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-91 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-91 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 6.0.0 > Environment: Designer build 3045 running on Windows > Reporter: Warren Gibson > Assignee: Dan Florian > Priority: Minor > Fix For: 6.0.0 > > Attachments: ScreenShot024.JPG > > > 1. Deleted Parts project in Model Explorer. > 2. As can be seen in ScreenShot024 the PartsSupplier vdb editor is still open > and showing a query for PartsSupplier. > 3. I would suggest when a project is closed or deleted all the associated editors should also be closed. -- 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

16 years, 8 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 March 2009