[JBoss JIRA] (TEIIDDES-1955) Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1955?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1955:
--------------------------------
Assignee: Mark Drilling (was: Ted Jones)
> Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-1955
> URL: https://issues.jboss.org/browse/TEIIDDES-1955
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> "No difference report was found" Error
> I am trying to test SAP NW-GATEWAY OData with DV6-ER4 and JDBS 7.0.1.GA/Designer 8.3.0-CR1
> The following steps will reproduce the error:
> 1. Do an import/Designer/Teiid Connection >> Source Model
> 2. Create a new datasource using webservice from available drivers
> 3. Enter Data Source Properties (can connect to the url in a browser):
> URL: https://sapes1.sapdevcenter.com/sap/opu/odata/IWFND/RMTSAMPLEFLIGHT/
> WebService Security Used: HTTPBasic
> class-name: used prefilled default
> Authentication User Name: P1940027560
> Authentication User Password: Foxrun1004
> 4. Selected the newly created driver and selected "Next"
> 5. Selected sap-nw-gateway translator and named the target model and selected "Next"
> 6. Was presented with a DDL screen and selected "Next"
> 7. The "Select the Differences to Apply" screen shows an Import Message "Error
> encountered while importing the DDL - No difference report was found". screenshot attached.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage.setVisible(DdlImportDifferencesPage.java:217)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:120)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:333)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:455)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:365)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:198)
> 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:174)
> 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)
> Root exception:
> java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:120)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:333)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:455)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:365)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:198)
> 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:174)
> 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)
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1969) Newly Created VDB Editor Does Not Show UDF JAR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1969?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-1969:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1036644
> Newly Created VDB Editor Does Not Show UDF JAR
> ----------------------------------------------
>
> Key: TEIIDDES-1969
> URL: https://issues.jboss.org/browse/TEIIDDES-1969
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
>
> Using Teiid Designer:
> Description of problem:
> I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created.
> Version-Release number of selected component (if applicable):
> DV 6.0.0 ER4
> JBDS 7.1.0 CR1
> JBIS 4.1.3 Beta5
> Teiid Designer 8.3.0 CR1
> OS X 10.9
> How reproducible:
> Always.
> Steps to Reproduce (using the E2EYahooUdfTestScript):
> 1. New > Teiid VDB
> 2. Select models from workspace. One of which is relational function with UDF JAR.
> 3. Click on "UDF Jars" tab of the VDB editor.
> Actual results:
> The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model.
> Expected results:
> The UDF JAR file should be displayed when the VDB is first created.
> Additional info:
> If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1969) Newly Created VDB Editor Does Not Show UDF JAR
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-1969:
-------------------------------------
Summary: Newly Created VDB Editor Does Not Show UDF JAR
Key: TEIIDDES-1969
URL: https://issues.jboss.org/browse/TEIIDDES-1969
Project: Teiid Designer
Issue Type: Bug
Components: Editors
Affects Versions: 8.3
Reporter: Van Halbert
Assignee: Barry LaFond
Using Teiid Designer:
Description of problem:
I created a VDB and added models from the workspace. One of these models, was a relational function model that had a UDF JAR associated with it. When the VDB is created and the VDB editor is shown for the first time, selecting the "UDF Jars" tab does not show the UDF JAR that was added to the VDB when the VDB was created.
Version-Release number of selected component (if applicable):
DV 6.0.0 ER4
JBDS 7.1.0 CR1
JBIS 4.1.3 Beta5
Teiid Designer 8.3.0 CR1
OS X 10.9
How reproducible:
Always.
Steps to Reproduce (using the E2EYahooUdfTestScript):
1. New > Teiid VDB
2. Select models from workspace. One of which is relational function with UDF JAR.
3. Click on "UDF Jars" tab of the VDB editor.
Actual results:
The "UDF Jars" tab of VDB editor does not show the UDF JAR file associated with the relational function model.
Expected results:
The UDF JAR file should be displayed when the VDB is first created.
Additional info:
If the VDB editor is closed and reopened, the UDF JAR is shown in the editor. So it is obviously being added to the VDB.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1968) VDB Editor - Multi Source editor binding issue - exceptions editing jndi column
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-1968:
---------------------------------------
Summary: VDB Editor - Multi Source editor binding issue - exceptions editing jndi column
Key: TEIIDDES-1968
URL: https://issues.jboss.org/browse/TEIIDDES-1968
Project: Teiid Designer
Issue Type: Bug
Components: Editors
Affects Versions: 8.3
Reporter: Mark Drilling
Assignee: Mark Drilling
Fix For: 8.3
Encountered the following exception when attempting to edit JNDI value:
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at org.teiid.designer.runtime.adapter.JBossServerUtil.isHostConnected(JBossServerUtil.java:55)
at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isJBossServerConnected(JBoss7ServerUtil.java:77)
at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.isParentServerConnected(TeiidServerAdapterFactory.java:276)
at org.teiid.designer.runtime.TeiidServer.isParentConnected(TeiidServer.java:332)
at org.teiid.designer.runtime.TeiidServer.isConnected(TeiidServer.java:314)
at org.teiid.designer.runtime.ui.connection.VdbSourceConnectionHandler.getDataSourceJndiNames(VdbSourceConnectionHandler.java:230)
at org.teiid.designer.vdb.ui.editor.panels.ModelDetailsPanel$JndiEditingSupport.refreshItems(ModelDetailsPanel.java:544)
at org.teiid.designer.ui.common.table.ResourceEditingSupport.getCellEditor(ResourceEditingSupport.java:84)
The server had been started from within the application (not externally)
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1940) Preview failed in case if [external] server restarted independent of Designer
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1940?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1940:
-----------------------------------------
Unable to reproduce. Please attach steps to reproduce TEIIDDES-1939, then it may lead to this. However, I can not repro either one.
> Preview failed in case if [external] server restarted independent of Designer
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-1940
> URL: https://issues.jboss.org/browse/TEIIDDES-1940
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.3
> Environment: Fedora 18, Oracle JDK 1.6
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> Steps
> 1) I kept seeing the TEIIDDES-1939 after the model creation, so logged into admin console using URI http://localhost:8080, with intention of deleting the datasource manually. I did not find the data source there.
> 2) Console said "reload is required" in its messages, so I choose to reload the server from Admin Console
> 3) Now back on the Designer, I selected my view table and previewed and received the following exception.
> The Designer before preview needs to make sure the needed VDB deployed to the connected server.
> {code}
> org.teiid.jdbc.TeiidSQLException: TEIID40046 VDB "PREVIEW_052e68a6-b711-4e7d-903f-1957fd7e9ff1_RecursiveXMLTest_project" version "latest" does not exist.
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:56)
> at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107)
> at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:1)
> at org.teiid.datatools.connectivity.TeiidJDBCConnection.createConnection(TeiidJDBCConnection.java:103)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.teiid.datatools.connectivity.TeiidJDBCConnectionFactory.createConnection(TeiidJDBCConnectionFactory.java:23)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.getSqlConnection(PreviewDataWorker.java:620)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.internalRun(PreviewDataWorker.java:397)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker.run(PreviewDataWorker.java:262)
> at org.teiid.designer.runtime.ui.preview.PreviewTableDataContextAction.run(PreviewTableDataContextAction.java:99)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-1966 at 12/2/13 4:49 PM:
----------------------------------------------------------------
I can edit all three columns and don't have the issue, as long as I use the tab key, and not the enter key.
However, if I clicked on one column, then clicked another column, without hitting the tab or enter key, it did hang.
was (Author: van.halbert):
I can edit all three columns and don't have the issue, as long as I use the tab key, and not the enter key.
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-1966:
---------------------------------------
I can edit all three columns and don't have the issue, as long as I use the tab key, and not the enter key.
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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
10 years, 7 months
[JBoss JIRA] (TEIIDDES-1966) Failed in Making a Multi-source Binding
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1966?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1966:
----------------------------------------
I just took any VDB with source model, and flipped to the Source Bindings tab, and checked multi-source then clicked add to see the behavior. The designer kind of locks up for while once I do that.
> Failed in Making a Multi-source Binding
> ---------------------------------------
>
> Key: TEIIDDES-1966
> URL: https://issues.jboss.org/browse/TEIIDDES-1966
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 8.2
> Environment: Mac OS X 10.9, Eclipse
> Reporter: yapeng shen
> Assignee: Barry LaFond
> Labels: regression
> Fix For: 8.3
>
>
> I've found out the multi-source binding support section in Teiid Designer User Guide 8.2, Chapter 9.
>
> In my testing project, I made a flat file data source and model. It's OK to query through VDB. Then I wanted to integrate another flat file in the same schema, which can be applied with multi-source binding support.
>
> As the User Guide pdf said, I clicked the VDB editor's Model tab, and then Source Binding Definition tab. I clicked the Multi-source check box and added a new source. Then a new tuple was added in the table, but among the three columns(source name, JNDI Name and Translator Name), only one can be edited till eclipse turns into a no-response state.
--
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
10 years, 7 months