September 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1453) Installable project examples need to get updated

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1453?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1453: ----------------------------------- Assignee: Mark Drilling (was: Barry LaFond) > Installable project examples need to get updated > ------------------------------------------------ > > Key: TEIIDDES-1453 > URL: https://issues.jboss.org/browse/TEIIDDES-1453 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 7.7.1 > Environment: Fedora 16 > Reporter: Paul Nittel > Assignee: Mark Drilling > Priority: Minor > Fix For: 8.2.x-prod-eds6.0 > > Attachments: FunkyChars.png, NewServerOutOfDate.png > > > The HTML help for the Web services demo displays off characters and has some out-of-date screenshots. See the attached for examples. > Also, for 8.2, Server menus and editors have changed. Need to update workflow to 8.2 tooling -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1769) EAP6 with Teiid 8.4 can not start in JBDS6

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1769?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1769. ------------------------------------ Resolution: Rejected Designer 8.1 was an intermediate release and did not fully integrate Teiid 8.4 and required server changes. Also, JBDS 6.0 (Eclipse Juno) was only supported by Designer 8.0, another intermediate release. Rejecting. Re-log if issues arise with JBDS 7.x, EAP 6.1 + Teiid 8.4 or greater and Designer 8.2 or greater. > EAP6 with Teiid 8.4 can not start in JBDS6 > ------------------------------------------ > > Key: TEIIDDES-1769 > URL: https://issues.jboss.org/browse/TEIIDDES-1769 > Project: Teiid Designer > Issue Type: Bug > Environment: JBDS6, EAP 6.1alpha, Teiid 8.4, Teiid designer 8.1, java sun 1.6, Fedora 18 > Reporter: Lucie Fabrikova > Attachments: eap6-jbds6-teiidserverconfig.png > > > I encountered following problem: I tried to start EAP 6.1 with Teiid 8.4 in JBDS6. The server started, but the "Teiid Server Configuration" couldn't be loaded and multiple problems occured (viz attachment). > Log (part): > - Error occurred during status handling: > java.lang.NullPointerException > at org.teiid.designer.runtime.ui.views.TeiidServerContentProvider$1$1.run(TeiidServerContentProvider.java:229) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3537) > - FrameworkEvent ERROR: > org.osgi.framework.BundleException: Exception in org.teiid.designer.runtime.ui.DqpUiPlugin.stop() of bundle org.teiid.designer.dqp.ui. > at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:791) > at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) > at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:566) > - An internal error occurred during: "Starting JBoss 7.1 Runtime Server". > java.lang.OutOfMemoryError: unable to create new native thread > - Application error: > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.RuntimeException: Active workbench window being requested but is not available. This is most certainly a programming bug.) > at org.eclipse.swt.SWT.error(SWT.java:4361) > at org.eclipse.swt.SWT.error(SWT.java:4276) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3537) -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-967) Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-967: --------------------------------------- Re-visit in Komodo design to see if it makes sense to organize all Schema child types into more DTP JDBC-like containment/folders > Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-967 > URL: https://issues.jboss.org/browse/TEIIDDES-967 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Van Halbert > Fix For: Komodo > > > When keys/indexes are listed, they get in the way of viewing. They should be placed into their own folder. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-967) Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-967?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-967: ---------------------------------- Fix Version/s: Komodo > Usability: Indexes/Keys should be placed into their own folder, because they just add to unnecessary scolling when they are not used for data access > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-967 > URL: https://issues.jboss.org/browse/TEIIDDES-967 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Van Halbert > Fix For: Komodo > > > When keys/indexes are listed, they get in the way of viewing. They should be placed into their own folder. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-750) The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-750?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-750. --------------------------------- Resolution: Rejected Paradigm is still too different. Rejecting > The ability to execute a Teiid VDB seems in conflict with the Run As... option in JBDS > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-750 > URL: https://issues.jboss.org/browse/TEIIDDES-750 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Fix For: Future > > > If you open the context menu for a VDB, the top-level menu contains Run As..., Debug As..., and Modeling submenus. I have no idea how Debug As... would even apply, but Run As... certainly seems like the intuitive option to choose if you want to execute a VDB, especially considering the submenu contains the single entry Run on Server. But that, of course, isn't correct and produces nothing more than an error message about no resources being available to execute; the user is supposed to instead choose Modeling > Execute VDB to run the VDB on the server. It seems like we should remove the Execute option under the Modeling submenu and instead intercept the Run As... > Run on Server option to do the right thing, or alternatively, remove/disable the Run As.../Debug As... menu option when a VDB is selected. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-827) Provide the option to create a Connection Profile based on the connection info stored in the tags for a model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-827?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-827. --------------------------------- Resolution: Rejected will not be implemented based on discussion > Provide the option to create a Connection Profile based on the connection info stored in the tags for a model > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-827 > URL: https://issues.jboss.org/browse/TEIIDDES-827 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs, Editors > Affects Versions: 7.3 > Reporter: Van Halbert > Fix For: No Future > > > Provide the option to create a Connection Profile based on the connection info stored in the tags for a model. This would be useful when a model is passed on to someone else and they could create the connection profile with a click. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1251) Allow preview translators to have their properties changed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1251?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1251: ----------------------------------- Fix Version/s: Komodo > Allow preview translators to have their properties changed > ---------------------------------------------------------- > > Key: TEIIDDES-1251 > URL: https://issues.jboss.org/browse/TEIIDDES-1251 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Ramesh Reddy > Fix For: Komodo > > > Previewing may not represent what the user wants or in some situations may not work, such as needed MESSAGE vs. PAYLOAD settings for the WS translator. The user should be able to tweak the preview to match their desired settings. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1257) When in transformation editor, enable the ability to right click on an invalid function and create it

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1257?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1257: ----------------------------------- Fix Version/s: 8.3 > When in transformation editor, enable the ability to right click on an invalid function and create it > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1257 > URL: https://issues.jboss.org/browse/TEIIDDES-1257 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Reporter: Van Halbert > Fix For: 8.3 > > > When users are creating views (tables exists), they cut-n-paste a query in. But it contains database specific procedures/functions. It would a nice feature to enable the right click on the invalid procedure and allow it to be created, because the metadata is there to define the parameters. The only unknown is the result, but opening the function editor at this time could allow for setting that. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1257) When in transformation editor, enable the ability to right click on an invalid function and create it

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1257?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1257: ----------------------------------- Assignee: Mark Drilling > When in transformation editor, enable the ability to right click on an invalid function and create it > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1257 > URL: https://issues.jboss.org/browse/TEIIDDES-1257 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.3 > > > When users are creating views (tables exists), they cut-n-paste a query in. But it contains database specific procedures/functions. It would a nice feature to enable the right click on the invalid procedure and allow it to be created, because the metadata is there to define the parameters. The only unknown is the result, but opening the function editor at this time could allow for setting that. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1250) Need to improve the concept of how we're using and presenting the standard File and Web Service procedures

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1250?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1250: ----------------------------------- Fix Version/s: 8.3 > Need to improve the concept of how we're using and presenting the standard File and Web Service procedures > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1250 > URL: https://issues.jboss.org/browse/TEIIDDES-1250 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Barry LaFond > Priority: Critical > Fix For: 8.3 > > Attachments: TEIIDDES-1250.txt > > > As we're developing more and more importers and model generators that utilize or require a source model containing getText(), getTextFiles(), invoke() or invokeHTTP(), it seems that we're spending a lot of time: > 1) Re-coding the logic to generate them to utilize the "Source" or connection profile stored in them > 2) Explaining to the user that this is "Required" and how/why it's happening. > The ONLY reason user-intervention is required is because currently, a Source model is needed as the carrier of the specific FILE or WSDL URL information. (Used to create "Data Source") > If this File/WSDL URL info was NOT included in these source models, then we could create a Built-in FileFunctions.xmi Source model that's delivered with the product and included in a VDB ANY time it's required. > To make this happen, we'd need another mechanism to persist the connection information and that might be the "View Model" that contains the SQL that contains the actual "File" or "URL" definition. This sort of makes sense. > I know our current "Preview Data" and "Create Data Source" framework only works with Source models, but if we could change this behavior we would save a LOT of pain and anguish for the user AND us developers in the future. > Currently this would simplify 3 different import wizards, remove a couple of Options in the "New > Teiid Metadata Model > Relational" wizard use case and remove a step or two from EACH cheat sheet or section in the documentation. -- 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

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2013