[JBoss JIRA] (TEIIDDES-1542) Powerhub driver not working with Teiid
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1542?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1542:
-----------------------------------
Attachment: JdbcImportMetadataPage.java
Added null check to ResultSet check
> Powerhub driver not working with Teiid
> --------------------------------------
>
> Key: TEIIDDES-1542
> URL: https://issues.jboss.org/browse/TEIIDDES-1542
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.7
> Environment: Windows Vista 64 bit
> Reporter: Tanmoy Palit
> Assignee: Barry LaFond
> Priority: Blocker
> Attachments: JdbcImportMetadataPage.java
>
>
> Powerhub drvier which is com.lgc.dam.phs.client.jdbc.PhsJDBCDriver, is a custom JDBC driver from Landmark.
> Connection string looks like the following:
> jdbc:scwapi:<server_name>;<powerhub_user>;<passwd>;<database_instance><database_name;<username>;<dbpasswd>
> Getting the following error when Teiid Designer is used to consume the underlying database:
> Error:
> Unexpected exception while calling com.lgc.dam.phs.client.jdbc.PhsJDBCDatabaseMetaData.getTableTypes() and processing results on Acceptance PowerExplorer.CDSPROD
> Here is the complete stack trace for the error:
> java.lang.NullPointerException
> at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportMetadataPage.initializeInTransaction(JdbcImportMetadataPage.java:313)
> at com.metamatrix.modeler.internal.jdbc.ui.wizards.JdbcImportMetadataPage.setVisible(JdbcImportMetadataPage.java:238)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1260)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1239)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1228)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1226)
> 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:624)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
> at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
> 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.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> 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:344)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
> Squrriel SQL Client successfully connects to metadata and executes queries to this Powerhub data source using same PhsJDBC driver
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1547) Cannot call web service which is created from model without primary key
by Eiichi Nagai (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1547?page=com.atlassian.jira.plu... ]
Eiichi Nagai updated TEIIDDES-1547:
-----------------------------------
Attachment: TEIIDDES-1547_reproducer.zip
I attached a reproducer.
> Cannot call web service which is created from model without primary key
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1547
> URL: https://issues.jboss.org/browse/TEIIDDES-1547
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 7.7.1
> Environment: JBDS 5.0.1
> Reporter: Eiichi Nagai
> Attachments: TEIIDDES-1547_reproducer.zip
>
>
> The web service which is created from model without primary key (or Access Pattern) cannot be called by the following exceptions.
> {noformat}
> org.apache.cxf.interceptor.Fault: No binding operation info while invoking unknown method with params unknown.
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:60)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111)
> at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99)
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431)
> at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74)
> at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:599)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-985) Create Test script to exercise Teiid Designer Search wizards
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-985?page=com.atlassian.jira.plug... ]
Mark Drilling resolved TEIIDDES-985.
------------------------------------
Resolution: Done
Marking resolved - this has been completed.
> Create Test script to exercise Teiid Designer Search wizards
> ------------------------------------------------------------
>
> Key: TEIIDDES-985
> URL: https://issues.jboss.org/browse/TEIIDDES-985
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Documentation, Testing
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.1
>
> Attachments: DesignerSearchTestScript_Teiid7.odt, SearchProject.zip
>
>
> Teiid Designer has 4 "Search > Teiid Designer" wizard contributions.
> Write a test script to exercise all 4 wizards and include a Model Project Set that represents a large enough data set to test full or new full functionality for these features.
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-1549:
-------------------------------------
Issue Type: Bug (was: Feature Request)
> Web service (and possibly other) procedures fail validation
> -----------------------------------------------------------
>
> Key: TEIIDDES-1549
> URL: https://issues.jboss.org/browse/TEIIDDES-1549
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Attachments: PartsBeforeLunch_MPS.zip
>
>
> Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set.
> There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command.
> The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result.
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation
by Steven Hawkins (JIRA)
Steven Hawkins created TEIIDDES-1549:
----------------------------------------
Summary: Web service (and possibly other) procedures fail validation
Key: TEIIDDES-1549
URL: https://issues.jboss.org/browse/TEIIDDES-1549
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 8.0
Reporter: Steven Hawkins
Attachments: PartsBeforeLunch_MPS.zip
Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set.
There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command.
The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result.
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1549) Web service (and possibly other) procedures fail validation
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1549?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-1549:
-------------------------------------
Attachment: PartsBeforeLunch_MPS.zip
> Web service (and possibly other) procedures fail validation
> -----------------------------------------------------------
>
> Key: TEIIDDES-1549
> URL: https://issues.jboss.org/browse/TEIIDDES-1549
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.0
> Reporter: Steven Hawkins
> Attachments: PartsBeforeLunch_MPS.zip
>
>
> Paul created the attached model project set and received an error complaining that the web service operation procedure did not project any symbols. More than likely the CreateProcedureCommand.getResultSetColumns needs to be consulted to see if the procedure returns a result set.
> There was a change in the Teiid 8.2 code that clarified the difference between the projected symbols and result set columns for a procedure and remove the notion of the user command.
> The projected columns are expected to match the containing call, which can project out/inout/return parameters, while the result set columns must match the metadata if specified. When no result set columns have been set, Teiid assumes will set the result set columns to the results of one of the returnable statements and validate that all other returnable statements must match that result.
--
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
11 years, 6 months
[JBoss JIRA] (TEIIDDES-1548) Add GUI handling for permission conditions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1548?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-2325 to TEIIDDES-1548:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-1548 (was: TEIID-2325)
Affects Version/s: (was: 8.2)
Component/s: (was: Query Engine)
Fix Version/s: (was: 8.3)
> Add GUI handling for permission conditions
> ------------------------------------------
>
> Key: TEIIDDES-1548
> URL: https://issues.jboss.org/browse/TEIIDDES-1548
> Project: Teiid Designer
> Issue Type: Feature Request
> Reporter: Steven Hawkins
>
> A common request is to implement row based security. Teiid has added the ability to define a permission condition for this purpose:
> <permission>
> <resource-name>...</resource-name>
> <condition>sql</condition>
> ...
> </permission>
> The sql should resolve against the resource specified, ideally designer would check that as well.
> See TEIID-2311 and the reference for how these conditions are applied.
--
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
11 years, 6 months