[JBoss JIRA] (TEIIDDES-1955) Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1955?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1955:
---------------------------------------------------
wgibson(a)redhat.com changed the Status of [bug 1034475|https://bugzilla.redhat.com/show_bug.cgi?id=1034475] from ON_QA to VERIFIED
> 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
>
> Attachments: ODataVDB.vdb, SAPGateway.ddl
>
>
> "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
12 years, 3 months
[JBoss JIRA] (TEIIDDES-1963) Designer Create User Defined Function Dialog contains Result Set Tab
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1963?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1963:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035356|https://bugzilla.redhat.com/show_bug.cgi?id=1035356] from MODIFIED to ON_QA
> Designer Create User Defined Function Dialog contains Result Set Tab
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1963
> URL: https://issues.jboss.org/browse/TEIIDDES-1963
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Original Description below, however, investigation determined that UDF's should now allow creating Result Set children, so the Result Set tab needs to be removed.
> Description of problem:
> Following the E2E Yahoo UDF Test Script, I tried to create the UDF. When I got to the part to create the return parameter for the function the "Add" column button could not be enabled.
> 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:
> Happens every time.
> Steps to Reproduce:
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter a function "Name" and a "Java Class" (to get rid of error message)
> 4. Click the "Result Set" tab
> 5. There is no way to add a result set column
> Actual results:
> Unable to create a return parameter for relational UDF model. But the model can be created and the return parameter can be added later using the New Child menu option.
> Expected results:
> The "Add" button in the wizard should enable so that a return parameter can be entered.
> Additional info:
> None
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1962) Incorrect Wizard Error Message When Creating A User Defined Function
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1962?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1962:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035372|https://bugzilla.redhat.com/show_bug.cgi?id=1035372] from MODIFIED to ON_QA
> Incorrect Wizard Error Message When Creating A User Defined Function
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1962
> URL: https://issues.jboss.org/browse/TEIIDDES-1962
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Description of problem:
> After filling in the function name, the error message states "User defined function category is undefined." Filling in the "Function Category" does not change the error message. Once the "Java Class" is filled in the error message goes away.
> Turns out the "Function Category" isn't required at all.
> 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
> How reproducible:
> Steps to Reproduce :
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter a function "Name."
> 4. Wizard error message now shows "User defined function category is undefined"
> 5. Only way to get rid of this error message is to enter a "Java Class"
> Actual results:
> Incorrect, misleading error message.
> Expected results:
> A correct error message indicating the "Java Class" is missing.
> Additional info:
> None.
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1955) Unable to import SAP NW-Gateway OData using sap-nw-gateway translator
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1955?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1955:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1034475|https://bugzilla.redhat.com/show_bug.cgi?id=1034475] from MODIFIED to ON_QA
> 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
>
> Attachments: ODataVDB.vdb, SAPGateway.ddl
>
>
> "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
12 years, 3 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1861:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1042907|https://bugzilla.redhat.com/show_bug.cgi?id=1042907] from MODIFIED to ON_QA
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.3.1
>
> Attachments: Teiiddes-1861-screencapture.m4v
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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, 3 months
[JBoss JIRA] (TEIIDDES-1961) Create User Defined Wizard Displays The UDF Jar Path In Reverse Order From Entered Text
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1961?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1961:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035384|https://bugzilla.redhat.com/show_bug.cgi?id=1035384] from MODIFIED to ON_QA
> Create User Defined Wizard Displays The UDF Jar Path In Reverse Order From Entered Text
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1961
> URL: https://issues.jboss.org/browse/TEIIDDES-1961
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> Description of problem:
> If you enter "abc" in the "UDF Jar Path" field of the "Create User Defined Function" Wizard, the text is displayed "cba".
> 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
> How reproducible:
> Always.
> Steps to Reproduce:
> Using Designer:
> 1. Create a new relational model
> 2. New Child > Procedure > User Defined Function > OK
> 3. Enter text in the "UDF Jar Path" field
> Actual results:
> The UDF JAR path text is reversed.
> Expected results:
> The UDF JAR path is displayed as entered.
> Additional info:
> None.
--
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, 3 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 commented on TEIIDDES-1969:
---------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1036644|https://bugzilla.redhat.com/show_bug.cgi?id=1036644] from MODIFIED to ON_QA
> 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
> Fix For: 8.3
>
>
> 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
12 years, 3 months