[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents
by Greg Haber (JIRA)
XSD as Relational importer has problems with child elements with many parents
-----------------------------------------------------------------------------
Key: TEIIDDES-191
URL: https://jira.jboss.org/jira/browse/TEIIDDES-191
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Environment: Teiid Designer 6.0.0 official (14 May 2009) release
Reporter: Greg Haber
Attachments: address.xsd, person.xsd, person2.xml, person2.xsd
I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3).
Which is all well and good in theory, but in practice it seems to hit a number of problems
1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached.
2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father).
I've also attached some other example problem XSDs - person2.xsd, and address.xsd
Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1098) Procedure parameter name refactoring issues
by Steven Hawkins (Created) (JIRA)
Procedure parameter name refactoring issues
-------------------------------------------
Key: TEIIDDES-1098
URL: https://issues.jboss.org/browse/TEIIDDES-1098
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.4.2
Reporter: Steven Hawkins
Priority: Minor
I encountered a couple of issues when refactoring a procedure parameter name.
1. The procedure transformation sql is not updated with the new name. For example given a procedure with a parameter param and a definition that just returns that value:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT param AS foo;
END
refactoring to param1 leaves the select as "select param as foo" rather than updating to select param1 as foo. Note that if this is implemented, then aliases may need to be added to, e.g. "select param" would become "select param1 as param". There is existing logic in the Teiid ExpressionMappingVisitor to handle that.
2. If you undo the refactoring of the name, then even after a save and rebuild the model is still marked with an error. I had to edit the already valid SQL to clear the error.
--
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
12 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard
by Paul Nittel (JIRA)
Data types inported from flat file partially implemented in wizard
------------------------------------------------------------------
Key: TEIIDDES-1037
URL: https://issues.jboss.org/browse/TEIIDDES-1037
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.5
Reporter: Paul Nittel
The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement.
I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing.
Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point.
The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-1079) Create Import VDB wizard
by Barry LaFond (JIRA)
Create Import VDB wizard
------------------------
Key: TEIIDDES-1079
URL: https://issues.jboss.org/browse/TEIIDDES-1079
Project: Teiid Designer
Issue Type: Feature Request
Components: Editors, Modeling, VDB & Execution
Affects Versions: 7.5
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 7.6
For usability improvements and migration support, it would be great to be able to import a VDB into a workspace, extract the models from the VDB into a new project (along with the VDB) and allow the user to begin to start editing the models as if they were new.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-1066) Enable editing of the translator override when its being created, the name is not editable
by Van Halbert (JIRA)
Enable editing of the translator override when its being created, the name is not editable
------------------------------------------------------------------------------------------
Key: TEIIDDES-1066
URL: https://issues.jboss.org/browse/TEIIDDES-1066
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 7.4.2
Reporter: Van Halbert
Building multiple vdb's in a single project, so that each will have different overrides to the translator in order to test various conditions. However, the translator override that is created for each vdb is called the same name (i.e,. <translator_name>-1), giving an illusion that properties maybe shared between the two. Unfortunately, was unable to change the name of the translator override so that each vdb override was specific.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[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
12 years, 7 months
[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
12 years, 7 months