February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-281) Import WSDL as Web Svc allows viewing of WSDL, but there is no file association

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-281?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-275 to TEIIDDES-281: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-281 (was: JBEDSP-275) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > Import WSDL as Web Svc allows viewing of WSDL, but there is no file association > ------------------------------------------------------------------------------- > > Key: TEIIDDES-281 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-281 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 7.1 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > > I was importing the Amazon WSDL file - http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl - and found it had an error. I right-clicked the file in the imported to view the WSDL, but there was no editor associated with that file. I went to Windows > Preferences to add the association, but WSDL is not a known file type. > I think we need to add .wsdl and associate an editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-280) Update Count metadata property is not avaialble on the Web Service procedure

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-280?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-686 to TEIIDDES-280: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-280 (was: JBEDSP-686) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > Update Count metadata property is not avaialble on the Web Service procedure > ---------------------------------------------------------------------------- > > Key: TEIIDDES-280 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-280 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Johnny Verhaeg > > "Update Count" metadata is not available on the Web Service procedure, this is only available on the virtual procedures. This data is used at run time to determine if procedure is "readonly", or does "single" or "multiple" updates to the underlaying databases. If this property not available then by default it is assumed that "multiple" updates and subject to the transactional restrictions in the server and dqp. > Per SteveH, this property must be on any kind of procedure, may that be virtual, web and xml service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-279) UUID values being created and stored in memory for XSD Schema elements.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-279?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-215 to TEIIDDES-279: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-279 (was: JBEDSP-215) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: Westport) > UUID values being created and stored in memory for XSD Schema elements. > ----------------------------------------------------------------------- > > Key: TEIIDDES-279 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-279 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Barry LaFond > Assignee: Johnny Verhaeg > > Noticed that adding XML Document models to VDB and saving created validation errors indicating the XML Doc elements contained href's with UUID's to XSD elements that did NOT have uuid's in stored/saved models. > Talked to John and we are currently still creating UUID's for All schema model objects but just not "saving" them to file system. We need to fix this, of course. > The simple use case is to create take any Schema model and generate an XML Doc model from it and SAVE. The validation error won't show up unless you fix all errors (i.e. transformations) and add to a VDB and save, so there is probably a problem with Validation rules??? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-278) Designer Enhancement - Add a Join Builder

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-278?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1155 to TEIIDDES-278: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-278 (was: JBEDSP-1155) Component/s: (was: Designer) Fix Version/s: (was: Westport) (was: Future Versions) Affects Version/s: Future (was: Future Versions) > Designer Enhancement - Add a Join Builder > ----------------------------------------- > > Key: TEIIDDES-278 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-278 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Add a Join Builder to the Designer, similiar to the Criteria Builder, for creating inner, outer and ansi joins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-277) Importing from a JDBC datasource should show XA connector options

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-277?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-732 to TEIIDDES-277: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-277 (was: JBEDSP-732) Component/s: Import/Export (was: Designer) Affects Version/s: (was: 5.5.3) > Importing from a JDBC datasource should show XA connector options > ----------------------------------------------------------------- > > Key: TEIIDDES-277 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-277 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Minor > > Importing from Oracle provided me with a "Select Connector Binding Type" dialog listing on the Oracle 8 and Oracle ANSI connectors. XA should be on that list as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-276) improve WSDL importer accuracy

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-276?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-189 to TEIIDDES-276: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-276 (was: JBEDSP-189) Component/s: Import/Export (was: Designer) Fix Version/s: 7.1 (was: Westport) > improve WSDL importer accuracy > ------------------------------- > > Key: TEIIDDES-276 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-276 > Project: Teiid Designer > Issue Type: Task > Components: Import/Export > Reporter: Marc Shirley > Fix For: 7.1 > > > are we trying to do too much ourselves instead of leveraging some standard open source components - seems like somebody must have solved the problem of turn WSDL into accurate Java object heirarchy, and we can go from there... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-275) Designer should collect cost analysis statistics at import time, by default, for any data source that supports it

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-275?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-387 to TEIIDDES-275: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-275 (was: JBEDSP-387) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: Future (was: 5.5) > Designer should collect cost analysis statistics at import time, by default, for any data source that supports it > ----------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-275 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-275 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: Future > Reporter: Michael Walker > Assignee: Barry LaFond > > Performance can be dramatically improved if cost statistics are gathered at design time, which turns on cost-based optimizations at run time. However, the majority of Genentech users fail to remember to import this information, because it is not part of the standard import process. > When importing metadata from any data source, we should present users with the option to collect cost analysis statistics during import, so long as the data source supports it (or if MMX can calculate it synthetically). > Of course, we could inform users that cost analysis may take add some time to the import process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-274) Make it easier to double-click to drill down into the transformation for a given view model

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-274?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-384 to TEIIDDES-274: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-274 (was: JBEDSP-384) Component/s: Diagrams (was: Designer) Fix Version/s: (was: Westport) (was: Future Versions) Affects Version/s: Future (was: 5.5) > Make it easier to double-click to drill down into the transformation for a given view model > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-274 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-274 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: Future > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: deadarea.JPG > > Time Spent: 1 minute > Remaining Estimate: 0 minutes > > We have allocated a very small area of space on each view model that allows you to double-click and drill down into the transformation, but it's too difficult for new users to locate this area, and there's no visual indication of where it begins or ends. > This is very common issue among new Designer users. They want to double-click on a view, to display and/or edit its transformation. They try double-clicking on the middle of the view -- this highlights the columns and does not drill-down. They try clicking on the top of the view, on it's name -- this highlights the view name and does not drill-down. If they happen to leave the view or column highlighted, then they won't be able to drill-down, even if they do click the small area that allows for it. > They give up on double-clicking, and instead, right-click on the view and get a large menu of options. "Open" is buried about half-way down, so some of them don't have the patience to find it. Overall, the process is very frustrating for new users. We should make it much more straightforward to do common operations such as this one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-273) Importing different version of Yahoo Connector causes api.exception

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-273?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-839 to TEIIDDES-273: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-273 (was: JBEDSP-839) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: (was: Westport) > Importing different version of Yahoo Connector causes api.exception > ------------------------------------------------------------------- > > Key: TEIIDDES-273 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-273 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Environment: Windows > Reporter: Warren Gibson > Assignee: Barry LaFond > > Had a yahoo connector in Designer and tried to import a different version of yahoo connector and received the following error. To get around the problem I had to delete the existing yahoo connector, shut down designer, restart designer, and import the new version of yahoo connector. > com.metamatrix.admin.api.exception.AdminComponentException: Delete of Connector type "Yahoo Connector" failed. Currently in > use by a Connector Binding. > at > com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.deleteConnectorType(EmbeddedConfigurationService.java:917 > ) > at com.metamatrix.dqp.embedded.admin.DQPConfigAdminImpl.deleteConnectorType(DQPConfigAdminImpl.java:231) > 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 com.metamatrix.jdbc.EmbeddedConnection$1.invoke(EmbeddedConnection.java:121) > at $Proxy12.deleteConnectorType(Unknown Source) > at com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor.removeConnectorType(WorkspaceExecutor.java:325) > at > com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor$BindingListener.handleConnectorTypeEvent(WorkspaceExecutor.java:5 > 17) > at com.metamatrix.modeler.dqp.ui.workspace.WorkspaceExecutor$BindingListener.stateChanged(WorkspaceExecutor.java:492) > at com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.fireChangeEvent(ConfigurationManagerImpl.java:478) > at com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.saveConfigLocal(ConfigurationManagerImpl.java:151) > at > com.metamatrix.modeler.dqp.internal.config.ConfigurationManagerImpl.removeConnectorType(ConfigurationManagerImpl.java:321) > at > com.metamatrix.modeler.internal.dqp.ui.workspace.actions.DeleteConnectorTypeAction.run(DeleteConnectorTypeAction.java:72) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) > 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:1003) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > 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:386) > 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:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) > at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-272) Allow query plans to be viewed within Designer without requiring that all bindings start successfully

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-272?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-383 to TEIIDDES-272: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-272 (was: JBEDSP-383) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: (was: 5.5) > Allow query plans to be viewed within Designer without requiring that all bindings start successfully > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-272 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-272 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Michael Walker > Assignee: Barry LaFond > > Developers want to view query plans when designing their models. Unfortunately, there is no way to view the query plan without executing a VDB. Fortunately, VDBs can be executed within Designer, so the query plans can be viewed within SQLExplorer. > However, if any connector binding fails to start for a given VDB running in Designer, then no query plans can be generated. Even if you use "OPTION PLANONLY", you will receive the error "connector binding X failed to start" and no plan will be generated. > Query plans are valuable at design time, but we've required a runtime environment be fully available in order to view them. We should allow users to view query plans from within Designer, even when bindings fail to start, so long as "OPTION DEBUG" is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2010