[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1870:
----------------------------------------
[~blafond] With out TEIIDDES-1871, it is not a workable solution. If that is ModeShape error, either it needs to be fixed there or Designer should override that class and have a fix meanwhile. Yes, I have tested with exporting the DDL and moving the tables around, that works.
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1871) NPE While using DDL based importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1871?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1871:
-----------------------------------
Attachment: working_sap_flight.ddl
> NPE While using DDL based importer
> ----------------------------------
>
> Key: TEIIDDES-1871
> URL: https://issues.jboss.org/browse/TEIIDDES-1871
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Attachments: sap-flight.ddl, working_sap_flight.ddl
>
>
> While importing the OData translator based DDL, encountered the below NPE.
> {code}
> Caused by: java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:117)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:330)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:453)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:362)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:195)
> at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150)
> at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209)
> at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:152)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1870:
-----------------------------------
Assignee: Ramesh Reddy (was: Mark Drilling)
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1796) IllegalArgumentException when creating datasource from an imported Webservice source model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1796?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1796:
-----------------------------------
Fix Version/s: 8.3
Assignee: Paul Richardson (was: Barry LaFond)
> IllegalArgumentException when creating datasource from an imported Webservice source model
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1796
> URL: https://issues.jboss.org/browse/TEIIDDES-1796
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Fix For: 8.3
>
>
> After importing from a remote web service and creating the source and view models, tried to (right click on source model) create data source on teiid server (EAP 6.1 / Teiid 8.4.1) and had this issue:
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-07-25 16:59:24.847
> !MESSAGE Error creating data source for model CustomerRESTWebSvcSource.xmi
> !STACK 0
> java.lang.IllegalArgumentException: The argument value is not specified for value: ''
> at org.jboss.as.cli.operation.impl.DefaultOperationRequestBuilder.addProperty(DefaultOperationRequestBuilder.java:113)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1397)
> at org.teiid.adminapi.AdminFactory$AdminImpl.addConfigProperty(AdminFactory.java:308)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:297)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createDataSource(AdminFactory.java:412)
> at org.teiid84.runtime.ExecutionAdmin.getOrCreateDataSource(ExecutionAdmin.java:324)
> at org.teiid.designer.runtime.TeiidServer.getOrCreateDataSource(TeiidServer.java:551)
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:156)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1877) SWT Widget Displosed exception from TeiidServerEditor page
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1877?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1877.
------------------------------------
Resolution: Done
added isDisposed() check
> SWT Widget Displosed exception from TeiidServerEditor page
> ----------------------------------------------------------
>
> Key: TEIIDDES-1877
> URL: https://issues.jboss.org/browse/TEIIDDES-1877
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Not sure how, but the server editor page was disposed, but still listening....
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.SWT.error(SWT.java:4283)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:481)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:418)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2425)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.refreshDisplayValues(TeiidServerEditor.java:523)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.access$0(TeiidServerEditor.java:519)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor$1$1.run(TeiidServerEditor.java:138)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1879) Translator Override Properties dialog box show the properties for the data sources, it should show override properties for translator
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1879?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1879:
----------------------------------------
Your analysis is correct that currently Teiid did not expose any way provide translator override properties through "admin api". I created TEIID-2687 for this purpose, I will not sure we can target that for 8.4.1? I will put in 8.6
Right now there no option other than working off of simple properties off the Translator object.
> Translator Override Properties dialog box show the properties for the data sources, it should show override properties for translator
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1879
> URL: https://issues.jboss.org/browse/TEIIDDES-1879
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.3
>
>
> The translator overrides dialog box during the VDB construction, shows the properties for the data source (resource-adapter) not for translator.
> The translator properties can be obtained on admin api by
> Translator t = api.getTranslator("name");
> t.getProperties()
> Currently there is no metadata available on them they are just key/value pairs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (TEIIDDES-1879) Translator Override Properties dialog box show the properties for the data sources, it should show override properties for translator
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1879?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1879:
----------------------------------------
So back when we implemented this feature our goal was to provide property definition context to the translator overrides panel (i.e. data type, allowed values, default values, etc). We apparently misunderstood how this all should work and in particular, what data is returned on 2 runtime/admin methods
*Admin.getTemplatePropertyDefniitions()* "Get all of the available configuration Properties for the specified connector"
*Translator.getProperties()* (AdminObject) "Get the Configuration Properties that defines this process"
I now understand that even though Translators and ResourceAdapters are included in the Connector definition, their properties are defined and tracked in different forms. ResourcesAdapter property definitions are defined via XML configuration however Translator property definitions don't really exist.
So fundamentally, there isn't a way to ask a Translator for it's property definitions and what Designer will have to work with is:
* String properties only (Name/Value pairs)
* No way to show/tell the user what Translator properties are available ?
I'm assuming that if a user currently changes a "resource adapter" property that the translator will probably ignore it, unless the "key" is a lucky guess.
So is there any other recourse for Designer other than to drop the property definitions and work with simple Properties?
> Translator Override Properties dialog box show the properties for the data sources, it should show override properties for translator
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1879
> URL: https://issues.jboss.org/browse/TEIIDDES-1879
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.3
>
>
> The translator overrides dialog box during the VDB construction, shows the properties for the data source (resource-adapter) not for translator.
> The translator properties can be obtained on admin api by
> Translator t = api.getTranslator("name");
> t.getProperties()
> Currently there is no metadata available on them they are just key/value pairs
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months