[JBoss JIRA] (TEIIDDES-1793) NPE when clicking finish when importing File Source (XML)
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1793?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1793.
-------------------------------------
Assignee: Mark Drilling (was: Paul Richardson)
Resolution: Done
Found that the error only occurred when selecting to place the generated models into the /source and /view folders.
Fixed a path comparison issue in ModelWorkspaceImpl which was the root of the problem.
https://github.com/Teiid-Designer/teiid-designer/pull/212
> NPE when clicking finish when importing File Source (XML)
> ---------------------------------------------------------
>
> Key: TEIIDDES-1793
> URL: https://issues.jboss.org/browse/TEIIDDES-1793
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Mark Drilling
> Priority: Blocker
> Fix For: 8.2
>
> Attachments: CustomerRESTWebSvc.war, designer_NPE.tiff
>
>
> When going the import wizard for importing File Source (XML), and on the last panel, pressing Finish, cause an ERROR dialog to be presented with no content. Looking in the log, see this stack trace:
> !ENTRY org.teiid.designer.transformation.ui 4 0 2013-07-23 11:11:33.479
> !MESSAGE Error creating tables in view model MyRESTViewModel
> !STACK 0
> java.lang.NullPointerException
> at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlFileImportProcessor.addProcedureToRelationalSourceModel(TeiidXmlFileImportProcessor.java:141)
> at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportProcessor.createProceduresInExistingSourceModelInTxn(TeiidMetadataImportProcessor.java:315)
> at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportProcessor.access$1(TeiidMetadataImportProcessor.java:310)
> at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportProcessor$1.execute(TeiidMetadataImportProcessor.java:79)
> at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.transformation.ui.wizards.file.TeiidMetadataImportProcessor.execute(TeiidMetadataImportProcessor.java:94)
> at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlImportWizard$1.run(TeiidXmlImportWizard.java:81)
> at org.teiid.designer.ui.common.util.UiUtil.runInSwtThread(UiUtil.java:492)
> at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlImportWizard.finish(TeiidXmlImportWizard.java:78)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> 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.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.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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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.ui.internal.actions.CommandAction.run(CommandAction.java:171)
> at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97)
> at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168)
> 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, 9 months
[JBoss JIRA] (TEIIDDES-1765) StateInfo example does not succeed
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1765?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1765:
----------------------------------------
Looks like Teiid-side issue??
> StateInfo example does not succeed
> ----------------------------------
>
> Key: TEIIDDES-1765
> URL: https://issues.jboss.org/browse/TEIIDDES-1765
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
>
> Walked thru the StateInfo example, and when I went to execute
> 12:55:47,190 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for {http://www.teiid.org/stateService/}stateService#{http://www.teiid.org/stateService/}GetAllStateInfo has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:237)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:95)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:145)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> 12:55:47,195 WARN [org.teiid.CONNECTOR] (Worker7_QueryProcessorQueue27) Connector worker process failed for atomic-request=VUNHCCMa+sUf.0.9.3: org.teiid.translator.TranslatorException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:139)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:254) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:446) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:159) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:156) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_13]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_13]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.0.Final.jar:8.4.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
> Caused by: javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.jaxws.DispatchImpl.mapException(DispatchImpl.java:287)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:392)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:243)
> at org.teiid.translator.ws.WSProcedureExecution.execute(WSProcedureExecution.java:135)
> ... 13 more
> Caused by: org.apache.cxf.binding.soap.SoapFault: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:75)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:46)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:35)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:114)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:69)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:34)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:800)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1696)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1532)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1440)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:659)
> at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:463)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:366)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
> at org.apache.cxf.endpoint.ClientImpl.invokeWrapped(ClientImpl.java:354)
> at org.apache.cxf.jaxws.DispatchImpl.invoke(DispatchImpl.java:385)
> ... 15 more
> 12:55:47,199 WARN [org.teiid.PROCESSOR] (Worker6_QueryProcessorQueue28) TEIID30020 Processing exception for request VUNHCCMa+sUf.0 'TEIID30504 stateService: Unexpected wrapper element GetAllStateInfo found. Expected {http://www.teiid.org/stateService/}GetAllStateInfo.'. Originally TeiidProcessingException Soap11FaultInInterceptor.java:75. Enable more detailed logging to see the entire stacktrace.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1720) Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1720?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1720:
----------------------------------------
No, what I am saying is when user is using the DDL importer, when he/she selects the File translator, use same technique as today and get the ddl metadata for source then follow on the DDL importer with the file format wizard for generated SQL. The same could be done for the web service wizard.
This also eliminates two other separate importers and consolidates them into single importer.
> Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
> ------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1720
> URL: https://issues.jboss.org/browse/TEIIDDES-1720
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export, Modeling
> Affects Versions: 7.8
> Reporter: Van Halbert
>
> When importing a text file, a model is created that has 1 procedure call in it, the getTextFiles() procedure. Would it be possible to get rid of this model and have the view model that references this, to call a System procedure?
> I'm not sure if this has already been done in Designer 8.x.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1720) Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1720?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1720:
----------------------------------------
It is not a system function, so we can not do it. IMO, the way to tackle this is to "embed" the TextTable creation wizard in the DDL importing wizard's flow such that you create the source model from Teiid and create the view model from wizard.
> Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
> ------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1720
> URL: https://issues.jboss.org/browse/TEIIDDES-1720
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export, Modeling
> Affects Versions: 7.8
> Reporter: Van Halbert
>
> When importing a text file, a model is created that has 1 procedure call in it, the getTextFiles() procedure. Would it be possible to get rid of this model and have the view model that references this, to call a System procedure?
> I'm not sure if this has already been done in Designer 8.x.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1794) Designer support for global temporary tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1794?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-2594 to TEIIDDES-1794:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-1794 (was: TEIID-2594)
Component/s: Modeling
(was: Query Engine)
Fix Version/s: (was: 8.5)
> Designer support for global temporary tables
> --------------------------------------------
>
> Key: TEIIDDES-1794
> URL: https://issues.jboss.org/browse/TEIIDDES-1794
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
>
> Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table.
> Alternatively extension metadata could be used.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1794) Designer support for global temporary tables
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1794?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-1794:
-------------------------------------
Assignee: (was: Steven Hawkins)
> Designer support for global temporary tables
> --------------------------------------------
>
> Key: TEIIDDES-1794
> URL: https://issues.jboss.org/browse/TEIIDDES-1794
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Mark Addleman
>
> Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table.
> Alternatively extension metadata could be used.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1720) Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1720?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1720:
----------------------------------------
The current requirement is for a File Data Source be created/deployed that represents a "file location". Teiid, I think, requires the "metadata" for the getTextFiles() procedure to be included in a VDB along with the corresponding JNDI name to the File Data Source.
If getTextFiles() was a system function, the data source info would have to be injected into a VDB in a different way?
Seems like this would need a lot of thought to change the current framework.... unfortunately
> Would it be possible to remove the need to create the getTextFiles() procedure and make it a System function
> ------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1720
> URL: https://issues.jboss.org/browse/TEIIDDES-1720
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export, Modeling
> Affects Versions: 7.8
> Reporter: Van Halbert
>
> When importing a text file, a model is created that has 1 procedure call in it, the getTextFiles() procedure. Would it be possible to get rid of this model and have the view model that references this, to call a System procedure?
> I'm not sure if this has already been done in Designer 8.x.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1767) Cannot redeploy a vdb with webservice datasource
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1767?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1767:
----------------------------------------
It will happen whenever you use previously used name for creating a resource adapter (webservice, file, ldap, google, ldap, salesforce) in lifespan of server instance.
> Cannot redeploy a vdb with webservice datasource
> ------------------------------------------------
>
> Key: TEIIDDES-1767
> URL: https://issues.jboss.org/browse/TEIIDDES-1767
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Paul Richardson
> Assignee: Ted Jones
> Fix For: 8.2
>
>
> When redeploying a vdb that contains a WSDL webservice, the following behaviour is observed.
> 1. Delete all vdb's data sources, including the WSDL webservice data source;
> 2. Deploy the vdb
> 3. Observe the following error
> {code}
> !ENTRY org.teiid.designer.dqp.ui 4 0 2013-06-27 10:18:06.314
> !MESSAGE TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> !STACK 0
> org.teiid.adminapi.AdminProcessingException: TEIID70006 JBAS014749: Operation handler failed: Service jboss.resourceadapters.ra.webservice.StockQuote is already registered
> at org.teiid.adminapi.AdminFactory$ResultCallback.onFailure(AdminFactory.java:195)
> at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1409)
> at org.teiid.adminapi.AdminFactory$AdminImpl.createConnectionFactory(AdminFactory.java:277)
> 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.TeiidDataSourceFactory.createDataSource(TeiidDataSourceFactory.java:107)
> at org.teiid.designer.runtime.ui.vdb.VdbDeployer.deploy(VdbDeployer.java:239)
> at org.teiid.designer.runtime.ui.actions.DeployVdbAction$1.run(DeployVdbAction.java:286)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
> Despite 'StockQuote' being deleted in step 1, the JBoss server still has it cached in a map so throws back this error. The client does not show it and connecting to the server via the cli also fails to show it. Restarting the server flushes the cache and the vdb can be successfully redeployed.
> Whether this should be passed to Teiid (are they responsible for flushing the cache?) or WireFly (not properly flushing the cache or data source deletion) is the question...
--
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, 9 months