February 2009 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-86?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-86: --------------------------------- Component/s: Diagrams Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Make page-up and page-down work in the model's Package Diagram > -------------------------------------------------------------- > > Key: TEIIDDES-86 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-86 > Project: Teiid Designer > Issue Type: Feature Request > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Optional > Fix For: 6.1.0 > > > 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 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-97) Confusing behavior of Preview Data action on diagram toolbar

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-97?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-97: --------------------------------- Component/s: Data Preview Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Confusing behavior of Preview Data action on diagram toolbar > ------------------------------------------------------------ > > Key: TEIIDDES-97 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-97 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: 6.1.0 > > > The behavior of the previewData action on the diagram toolbar is sometimes confusing. This is occurring because the action enablement is driven by workspace selection, but when you click the diagram toolbar action the first thing that happens is that focus is driven to the diagram - which may not have a selected table. This results in no data being returned. > 1) Open a package diagram. In my case the package diagram was at the level of a schema and nothing selected. > 2) Select a table in model explorer. both the model explorer and diagram toolbar preview buttons enable. > 3) click the model explorer preview button. Data is returned. > 4) click the diagram toolbar preview button. No data returned. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-95) Designer: UserFiles tab in VDB Editor - allow "Add from Workspace" and DragnDrop

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-95?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-95: --------------------------------- Component/s: Editors Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Designer: UserFiles tab in VDB Editor - allow "Add from Workspace" and DragnDrop > -------------------------------------------------------------------------------- > > Key: TEIIDDES-95 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-95 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: 6.1.0 > > > Allow user to more easily add files from their workspace via button or drag n drop. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-84) Description View And Transformation Editor Background Color Does Not Update When Changing Resource Readonly State Until Workspace Selection

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-84?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-84: --------------------------------- Component/s: Views Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Description View And Transformation Editor Background Color Does Not Update When Changing Resource Readonly State Until Workspace Selection > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-84 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-84 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 6.0.0 > Environment: Windows, Linux > Reporter: Dan Florian > Priority: Minor > Fix For: 6.1.0 > > > When using the resource properties dialog to change the readonly state of a resource, the background color should change immediately in the Description View and Transformation Editor (and possibly other views/editors that use the StyledText widget). The background does eventually change when a new workspace selection event occurs. We are getting notified of the readonly state change when it happens but everything I've tried (control.redraw(), control.update()) has not worked. I've also tried generating a paint event using the Display but that wasn't working either. The view/editor do not allow the user to "modify" the readonly resource so marked bug as minor. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-106) No Need To Have Built-In (Reserved) Connector Jar Names

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-106?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-106: ---------------------------------- Component/s: Teiid Integration Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > No Need To Have Built-In (Reserved) Connector Jar Names > ------------------------------------------------------- > > Key: TEIIDDES-106 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-106 > Project: Teiid Designer > Issue Type: Task > Components: Teiid Integration > Affects Versions: 6.0.0 > Reporter: Dan Florian > Assignee: Dan Florian > Fix For: 6.0.0 > > > In 5.5.3 and prior, the Designer had a set of built-in connector jars. The Designer had a requirement that the user could not import connector or UDF jar having a name of one of those built-in jars. For Westport that requirement is gone because of changes to the DQP. Numerous classes have methods or reference methods written for this concept. All code pertaining to the built-in connector jars should be removed. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-106) No Need To Have Built-In (Reserved) Connector Jar Names

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-106?page=com.atlassian.jira.p... ] Barry LaFond reassigned TEIIDDES-106: ------------------------------------- Assignee: Dan Florian (was: Barry LaFond) > No Need To Have Built-In (Reserved) Connector Jar Names > ------------------------------------------------------- > > Key: TEIIDDES-106 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-106 > Project: Teiid Designer > Issue Type: Task > Reporter: Dan Florian > Assignee: Dan Florian > > In 5.5.3 and prior, the Designer had a set of built-in connector jars. The Designer had a requirement that the user could not import connector or UDF jar having a name of one of those built-in jars. For Westport that requirement is gone because of changes to the DQP. Numerous classes have methods or reference methods written for this concept. All code pertaining to the built-in connector jars should be removed. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-81) Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-81?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-81: --------------------------------- Fix Version/s: 6.1.0 (was: 6.0.0) > Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-81 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-81 > Project: Teiid Designer > Issue Type: Feature Request > Environment: Enterprise Designer in Linux and Windows > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 6.1.0 > > > If you bring an existing VDB with Connector bindings assigned into the Designer, those bindings are never added to the Configuration Manager. They appear as if they are there when you look at the Execute screen but they are not and you have to create new. This will be very confusing for any evaluation customers that we are sending the training materials with existing vdbs. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-79) Description info in source model not copied to view when built via transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-79?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-79: --------------------------------- Workaround Description: Copy entire model, then selectively delete unwanted model objects in new model. Fix Version/s: 6.1.0 (was: 6.0.0) Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Workaround: [Workaround Exists] > Description info in source model not copied to view when built via transformation > --------------------------------------------------------------------------------- > > Key: TEIIDDES-79 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-79 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 6.1.0 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > I imported Books from a relational source and added a few descriptions to some columns. I then created a new relational view model, using the optional builder to transform from an existing model. All metadata was copied correctly EXCEPT the descriptions. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Deleted: (TEIIDDES-114) Remove ability to perform partial copy model operations in new model wizard.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-114?page=com.atlassian.jira.p... ] Barry LaFond deleted TEIIDDES-114: ---------------------------------- > Remove ability to perform partial copy model operations in new model wizard. > ---------------------------------------------------------------------------- > > Key: TEIIDDES-114 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-114 > Project: Teiid Designer > Issue Type: Task > Reporter: Barry LaFond > Assignee: Barry LaFond > > Because the design is flawed, this sub-feature continues to generate defects. > The purpose of this task is to remove this sub-feature. -- 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

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-114) Remove ability to perform partial copy model operations in new model wizard.

by Barry LaFond (JIRA)

Remove ability to perform partial copy model operations in new model wizard. ---------------------------------------------------------------------------- Key: TEIIDDES-114 URL: https://jira.jboss.org/jira/browse/TEIIDDES-114 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 6.0.0 Because the design is flawed, this sub-feature continues to generate defects. The purpose of this task is to remove this sub-feature. -- 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

15 years, 2 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 2009