April 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1321) Use Teiid Validation Logic in Designer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1321: ----------------------------------- Summary: Use Teiid Validation Logic in Designer Key: TEIIDDES-1321 URL: https://issues.jboss.org/browse/TEIIDDES-1321 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export, Transformations Affects Versions: 7.7 Reporter: Ted Jones Fix For: 7.7.1 We currently have column validation logic in the importers that generate transformations (XML and Web Service). If possible, we should leverage the Teiid validation logic to avoid duplication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1322) KRB5/GSSAPI Authentication support

by Graeme Gillies (JIRA)

Graeme Gillies created TEIIDDES-1322: ---------------------------------------- Summary: KRB5/GSSAPI Authentication support Key: TEIIDDES-1322 URL: https://issues.jboss.org/browse/TEIIDDES-1322 Project: Teiid Designer Issue Type: Feature Request Environment: Teiid Designer all versions Reporter: Graeme Gillies Hi, KRB5/GSSAPI authentication was added in Teiid Runtime 7.6 (see [1]) and this seems to work for both the JDBC and postgresql emulation layer. The problem is if you have a teiid instance secured by KRB5/GSSAPI and you wish to use the designer against it, you currently can't. This is because the "add teiid connection" screen takes a bunch of input and hand crafts the driver URL, which means you are unabled to add the extra jdbc url options needed such as authenticationType=KRB5;jaasName=Client;kerberosServicePrincipleName=demo(a)EXAMPLE.COM The add connection screen should be changed to either have a tick box to say "use gssapi authentication" and then allow you to specify the jaasName and kerberosServicePrincipalName, or it should have some way for you to add "custom jdbc url options" (or just allow you to manually craft the jdbc url). Regards, Graeme [1] https://issues.jboss.org/browse/TEIID-1610 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1320) Name field not populated when selecting existing source model in 'Import from XML Source'

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1320: ----------------------------------------- Summary: Name field not populated when selecting existing source model in 'Import from XML Source' Key: TEIIDDES-1320 URL: https://issues.jboss.org/browse/TEIIDDES-1320 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7 Reporter: Paul Richardson Assignee: Paul Richardson Priority: Minor Fix For: 7.7.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1315) Flat File Importer creates view model with column lengths not equal to those defined by the view's transformation query

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1315: ------------------------------------- Summary: Flat File Importer creates view model with column lengths not equal to those defined by the view's transformation query Key: TEIIDDES-1315 URL: https://issues.jboss.org/browse/TEIIDDES-1315 Project: Teiid Designer Issue Type: Bug Environment: JBDS 5.0 Beta 2 Reporter: Paul Nittel At the conclusion of using the flat file importer to create a view model, the column lengths of the model should be defined by the transformation SQL. In this case, all columns have a length of 10 despite the transformation specifying lengths of 5, 10, and 15. (See the attached screenshot.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (TEIIDDES-1301) Rename the "Web Services Data Source (non-SOAP)" to "Web Services Data Source (REST)"

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1301: ----------------------------------- Summary: Rename the "Web Services Data Source (non-SOAP)" to "Web Services Data Source (REST)" Key: TEIIDDES-1301 URL: https://issues.jboss.org/browse/TEIIDDES-1301 Project: Teiid Designer Issue Type: Task Components: Datatools Integration Affects Versions: 7.7 Reporter: Ted Jones Fix For: 7.7.1 We should rename the Web Services Data Source (non-SOAP) to New Web Services Data Source (REST). This will be more specific as to its intent and will be key to creating an importer for RESTFul services (including OData/SAP Gateway). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1316) (Flat file importer - fixed length) Defining a column with length of zero generates Unhandled event loop exception

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1316: ------------------------------------- Summary: (Flat file importer - fixed length) Defining a column with length of zero generates Unhandled event loop exception Key: TEIIDDES-1316 URL: https://issues.jboss.org/browse/TEIIDDES-1316 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Modeling Environment: JBS 5.0 beta 2 Reporter: Paul Nittel If the user accidently attempts to add a column with a length of zero, they generate an exception. A warning that the length must be > zero would be friendlier. eclipse.buildId=unknown java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.jbds.product.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product Error Fri Apr 13 09:31:08 CDT 2012 Unhandled event loop exception java.lang.IllegalArgumentException: width is zero or less at com.metamatrix.core.util.CoreArgCheck.isPositive(CoreArgCheck.java:88) at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidColumnInfo.<init>(TeiidColumnInfo.java:112) at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportOptionsPage.createColumn(TeiidMetadataImportOptionsPage.java:1177) at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportOptionsPage.access$6(TeiidMetadataImportOptionsPage.java:1171) at com.metamatrix.modeler.transformation.ui.wizards.file.TeiidMetadataImportOptionsPage$18.widgetSelected(TeiidMetadataImportOptionsPage.java:861) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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(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: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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (TEIIDDES-86) Make page-up and page-down work in the model's Package Diagram

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-86?page=com.atlassian.jira.plugi... ] Paul Richardson resolved TEIIDDES-86. ------------------------------------- Resolution: Done 7.7.x branch > Make page-up and page-down work in the model's Package Diagram > -------------------------------------------------------------- > > Key: TEIIDDES-86 > URL: https://issues.jboss.org/browse/TEIIDDES-86 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Paul Richardson > Priority: Optional > Fix For: 7.7.1 > > > Large model diagrams are difficult to navigate, in part because we have not implemented support for page-up and page-down. We've implemented it for other parts of Designer (e.g. Model Explorer tree) so we should implement it for the package diagram view as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1299) Displaying execution plan in empty SQL scrapbook displays error dialog

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1299: ----------------------------------------- Summary: Displaying execution plan in empty SQL scrapbook displays error dialog Key: TEIIDDES-1299 URL: https://issues.jboss.org/browse/TEIIDDES-1299 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.7 Environment: Fedora 16 teiid designer revision 2455 Reporter: Paul Richardson Priority: Minor As per documentation: 1) In ModelExplorer, select a previewable item, then Rt-click > Modeling > Show Execution Plan 2) In SQL Scrapbook, the Execution Plan is available after each query execution 3) In SQL Scrapbook, Rt-click > Teiid_7.x > Get Execution Plan If the scrapbook contains a query string then everything is fine. An empty scrapbook causes an error dialog to be displayed and the following stack trace in the console: !ENTRY org.teiid.datatools.connectivity.ui 4 0 2012-04-10 13:37:53.554 !MESSAGE An Error occurred fetching the Execution Plan. !STACK 0 org.teiid.jdbc.TeiidSQLException: Remote org.teiid.api.exception.query.QueryParserException: Parser cannot parse an empty sql statement. at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:113) at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:70) at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:617) at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:70) at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:537) at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130) at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37) at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:220) at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:255) at sun.reflect.GeneratedMethodAccessor34.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:110) at $Proxy18.read(Unknown Source) at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:349) at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:335) at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:546) at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:338) at org.teiid.datatools.connectivity.ui.plan.TeiidExplainSQLActionDelegate.getExecutionPlan(TeiidExplainSQLActionDelegate.java:230) at org.teiid.datatools.connectivity.ui.plan.TeiidExplainSQLActionDelegate.run(TeiidExplainSQLActionDelegate.java:181) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) Caused by: [TeiidProcessingException]Remote org.teiid.api.exception.query.QueryParserException: Parser cannot parse an empty sql statement. at org.teiid.query.parser.QueryParser.parseCacheHint(QueryParser.java:160) at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:481) at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:276) at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:215) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:232) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-86) Make page-up and page-down work in the model's Package Diagram

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-86?page=com.atlassian.jira.plugi... ] Paul Richardson updated TEIIDDES-86: ------------------------------------ Fix Version/s: 7.7.1 (was: 8.0) > Make page-up and page-down work in the model's Package Diagram > -------------------------------------------------------------- > > Key: TEIIDDES-86 > URL: https://issues.jboss.org/browse/TEIIDDES-86 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Michael Walker > Assignee: Paul Richardson > Priority: Optional > Fix For: 7.7.1 > > > Large model diagrams are difficult to navigate, in part because we have not implemented support for page-up and page-down. We've implemented it for other parts of Designer (e.g. Model Explorer tree) so we should implement it for the package diagram view as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-465) Trying to import wsdl as at Relation Model but unable to select a method

by Van Halbert (JIRA)

Trying to import wsdl as at Relation Model but unable to select a method ------------------------------------------------------------------------ Key: TEIIDDES-465 URL: https://jira.jboss.org/browse/TEIIDDES-465 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.3 Reporter: Van Halbert Trying to import the wsdl jrl_inquirywsdl.wsdl (in attached zip) using the import --> WSDL to Relational Model option. After selecting the wsdl from the file system, then validating, the next panel presented the methods to select (none-preselected). When you highlight a method, in the Select Details section it says: "The style for the service cannot be determined. " The next or finished button was never enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2012