November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1173) Problems With And Suggestions For The XML Source Importer

by Dan Florian (Created) (JIRA)

Problems With And Suggestions For The XML Source Importer --------------------------------------------------------- Key: TEIIDDES-1173 URL: https://issues.jboss.org/browse/TEIIDDES-1173 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.6 Environment: Teiid Designer 7.6 CR1 using Mac OS X 10.7.2 Reporter: Dan Florian Fix For: 7.6 Wizard Page 1: XML Data File Source Selection - Name text field positions caret back to the beginning after entering a character - when there is no name for the source model the model status message says "Source model does not exist." - Source model text field requires the ".xmi" extension to be entered before knowing that that model already exists. So you can continue on with the wizard if you leave off the ".xmi" even if there is a model with that name. Wizard Page 2: XML Data File Import Options Page - Selected XML Data File is editable - Could setting root path be done by a button and based on selection? Right now anything can be entered. - root path label should have a colon - splitters between the sections would be nice - Down and Up buttons remain enabled after pushing them even though there is not a selection (throws exception if pushed again) - seems like the Add button is misplaced. It should be under the xml tree since it is based on a tree selection. Maybe then "Add" could be changed to "Select As Column" or "Add as Column". - root path text field positions caret back to the beginning after entering a character - should Path be editable in Column Info? Not sure when editable how it works with root path. Wizard Page 3: View Model Definition Page - Selected data file is editable - Same problems with Name text field as other text fields. Also can't seem to delete selected characters or delete the last character. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1177) MED Editor - Documentation for 7.6 Release

by Barry LaFond (Created) (JIRA)

MED Editor - Documentation for 7.6 Release ------------------------------------------ Key: TEIIDDES-1177 URL: https://issues.jboss.org/browse/TEIIDDES-1177 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.6 Need documentation on the new framework. Maybe even a separate Users Guide? in addition to a section in the full users guide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
3
0 / 0

[JBoss JIRA] (TEIIDDES-1176) Usability Issue: On DDL importer, need better feed back when a file cannot be imported

by Van Halbert (Created) (JIRA)

Usability Issue: On DDL importer, need better feed back when a file cannot be imported -------------------------------------------------------------------------------------- Key: TEIIDDES-1176 URL: https://issues.jboss.org/browse/TEIIDDES-1176 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Van Halbert When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed. Also, it would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-695) Cannot paste into Table Editor cell via CTRL-V - get error msg and NPE

by Paul Nittel (JIRA)

Cannot paste into Table Editor cell via CTRL-V - get error msg and NPE ---------------------------------------------------------------------- Key: TEIIDDES-695 URL: https://jira.jboss.org/browse/TEIIDDES-695 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1.1 Environment: Windows, JBDS 4.0 Beta 1 Reporter: Paul Nittel Priority: Minor Fix For: 7.1.1 I tried to paste a value into a table editor column by CTRL-V and get an error and exception. I _am_ able to paste via right-click > Paste. (I used a relational source model/Columns tab.) Error 2010-10-29 09:53:53.453 Cannot set value "w00t" for the name property of this Column java.lang.NullPointerException at org.eclipse.emf.edit.provider.ItemProviderAdapter.getPropertyDescriptor(ItemProviderAdapter.java:258) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getPropertyValue(ModelObjectPropertySource.java:332) at com.metamatrix.modeler.internal.ui.table.ModelRowElement.setValue(ModelRowElement.java:244) at com.metamatrix.modeler.internal.ui.table.ModelTableEditor.pasteClipboardContents(ModelTableEditor.java:1400) at com.metamatrix.modeler.internal.ui.actions.TableClipboardPasteAction.doRun(TableClipboardPasteAction.java:41) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1253) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1103) at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1427) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1099) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1508) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4268) at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2175) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4160) at org.eclipse.swt.widgets.Text.windowProc(Text.java:2170) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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

14 years, 5 months

3
6
0 / 0

[JBoss JIRA] (TEIIDDES-1169) Should be able to add "sourcefunction" MED to any Relational source model

by Barry LaFond (Created) (JIRA)

Should be able to add "sourcefunction" MED to any Relational source model ------------------------------------------------------------------------- Key: TEIIDDES-1169 URL: https://issues.jboss.org/browse/TEIIDDES-1169 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.6 Reporter: Barry LaFond Priority: Blocker Fix For: 7.6 Should be able to add "sourcefunction" MED to any Relational source model. Salesforce MED shows up, but not source function MED -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1174) Unable to execute preview or VDB queries

by Mark Drilling (Created) (JIRA)

Unable to execute preview or VDB queries ---------------------------------------- Key: TEIIDDES-1174 URL: https://issues.jboss.org/browse/TEIIDDES-1174 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.6 Reporter: Mark Drilling Attempt to run a query from sql scrapbook in 7.6 CR1 results in the following exception: !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NoClassDefFoundError: Could not initialize class org.teiid.jdbc.StatementImpl at org.teiid.jdbc.DatabaseMetaDataImpl.getCatalogs(DatabaseMetaDataImpl.java:444) at org.eclipse.datatools.connectivity.sqm.loader.JDBCCatalogLoader.createResultSet(JDBCCatalogLoader.java:177) at org.eclipse.datatools.connectivity.sqm.loader.JDBCCatalogLoader.loadCatalogs(JDBCCatalogLoader.java:109) at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCDatabase.loadCatalogs(JDBCDatabase.java:101) at org.eclipse.datatools.connectivity.sqm.core.rte.jdbc.JDBCDatabase.getCatalogs(JDBCDatabase.java:63) at org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getDatabaseList(ProfileUtil.java:776) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.connection.AbstractConnectionInfoComposite.initDBNames(AbstractConnectionInfoComposite.java:156) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.connection.AbstractConnectionInfoComposite.init(AbstractConnectionInfoComposite.java:294) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.connection.ConnectionInfoComposite2.init(ConnectionInfoComposite2.java:267) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.connection.AbstractConnectionInfoComposite.init(AbstractConnectionInfoComposite.java:244) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.connection.AbstractConnectionInfoComposite.init(AbstractConnectionInfoComposite.java:254) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor.SQLScrapbookEditor$ToolbarSourceViewer.<init>(SQLScrapbookEditor.java:90) at org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor.SQLScrapbookEditor.doCreateSourceViewer(SQLScrapbookEditor.java:332) at org.eclipse.datatools.sqltools.sqleditor.SQLEditor.createSourceViewer(SQLEditor.java:868) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1148) Create Model Extension Definition Update Registry Action

by Dan Florian (Created) (JIRA)

Create Model Extension Definition Update Registry Action -------------------------------------------------------- Key: TEIIDDES-1148 URL: https://issues.jboss.org/browse/TEIIDDES-1148 Project: Teiid Designer Issue Type: Task Components: Editors, Views Affects Versions: 7.6 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.6 There is an action to add a selected Model Extension Definition (MED) to the registry. This action is accessed from the Model Extension Registry View and from the MED Editor. If the user wants to update an existing MED in the registry the user must perform a delete and then an add. The action should be changed to notice if the MED being registered is new or is one being updated. If it is an updated MED the user should be asked for overwrite confirmation. If the user tries to update a MED that is exactly equal to the registered MED the update should not occur and the user told why. Since right now both the MED namespace prefix and namespace URI must be unique in the registry an interesting, and hopefully infrequent scenario can occur: both the namespace prefix and namespace URI of the MED being registered exist already in the registry but are found in different MEDs. Do we allow an update in this case? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
3
0 / 0

[JBoss JIRA] (TEIIDDES-1089) SalesForce Connection Profile Should Default to HTTPS

by Ted Jones (Created) (JIRA)

SalesForce Connection Profile Should Default to HTTPS ----------------------------------------------------- Key: TEIIDDES-1089 URL: https://issues.jboss.org/browse/TEIIDDES-1089 Project: Teiid Designer Issue Type: Bug Components: Datatools Integration Affects Versions: 7.5 Reporter: Ted Jones The SalesForce connection profile uses http in it's default URL which cause the following error when creating a connection profile: java.lang.Exception: com.sforce.soap.partner.UnexpectedErrorFault: UNSUPPORTED_CLIENT: HTTPS Required at com.metamatrix.modeler.modelgenerator.salesforce.connection.impl.Connection.login(Connection.java:82) at org.teiid.designer.datatools.salesforce.SalesForceConnection.<init>(SalesForceConnection.java:48) at org.teiid.designer.datatools.salesforce.ConnectionFactory.createConnection(ConnectionFactory.java:11) at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83) at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:360) at org.teiid.designer.datatools.salesforce.ui.SalesForceProfileDetailsWizardPage$SalesforcePingJob.createTestConnection(SalesForceProfileDetailsWizardPage.java:405) at org.teiid.designer.datatools.salesforce.ui.SalesForceProfileDetailsWizardPage$SalesforcePingJob.run(SalesForceProfileDetailsWizardPage.java:392) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: com.sforce.soap.partner.UnexpectedErrorFault: UNSUPPORTED_CLIENT: HTTPS Required at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107) at $Proxy36.login(Unknown Source) at com.metamatrix.modeler.modelgenerator.salesforce.connection.impl.Connection.login(Connection.java:73) ... 7 more Overriding with the ssl version of the URL gets around this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
5
0 / 0

[JBoss JIRA] (TEIIDDES-1045) Teiid JDBC metadata import wizard does not show database schema checked when importing from MySQL

by Mark Drilling (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1045?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1045. ------------------------------------- Resolution: Cannot Reproduce Bug I could not reproduce. Will re-open if we can find a reproducible scenario. > Teiid JDBC metadata import wizard does not show database schema checked when importing from MySQL > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1045 > URL: https://issues.jboss.org/browse/TEIIDDES-1045 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.5 > Environment: RHEL 6, x84_64, OpenJDK 1.6 > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 7.6 > > > When importing JDBC metadata from a MySQL database, the connection profile specifies the database name (schema). However, on the Select Database Objects page (4th page), the database name specified in the connection URL is not automatically selected. The user must select the correct schema to proceed. It should default to the database specified in the connection profile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Barry LaFond (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1160: -------------------------------------- Assignee: Ted Jones (was: Barry LaFond) > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > Priority: Critical > Fix For: 7.6 > > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 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 November 2011