December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1499) XML document to web service

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1499?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1499. ---------------------------------- Resolution: Won't Do > XML document to web service > --------------------------- > > Key: TEIIDDES-1499 > URL: https://issues.jboss.org/browse/TEIIDDES-1499 > Project: Teiid Designer > Issue Type: Enhancement > Components: Web Services Support > Affects Versions: 7.7 > Reporter: luca gioppo > Priority: Minor > > There is a wizer for generating web service from relational model it should be nice to have one from a XML model > See: > https://community.jboss.org/message/761404#761404 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1353) Generate SQL for VDB Execute

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1353?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1353. ---------------------------------- Resolution: Won't Do > Generate SQL for VDB Execute > ---------------------------- > > Key: TEIIDDES-1353 > URL: https://issues.jboss.org/browse/TEIIDDES-1353 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 7.7 > Reporter: Ted Jones > Fix For: Future > > > When executing a VDB from Designer, we should determine possible SQL based on model information and persist in some way to make it available in SQL Scrapbook. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1309) Create Function model migration utility

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1309?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1309. ---------------------------------- Resolution: Out of Date Implemented via: TEIIDDES-2775 > Create Function model migration utility > --------------------------------------- > > Key: TEIIDDES-1309 > URL: https://issues.jboss.org/browse/TEIIDDES-1309 > Project: Teiid Designer > Issue Type: Sub-task > Components: Modeling > Affects Versions: 8.0 > Reporter: Barry LaFond > Attachments: New View Procedure Wizard.bmml, New View Procedure Wizard.png > > > In 8.0, users will no longer be able to use Function models in their VDB's. > This sub-task covers the work needed to create utilities in Teiid Designer to assist users in transforming their old Function models into the new way of defining functions via simple source or view model procedures that are flagged with "function = TRUE" property. > Work should cover the different scenarios a user may run into including: > * handling legacy VDBs > * Developing best practices for migrating function models -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1253) Save action takes the view back to package view

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1253?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1253. ---------------------------------- Resolution: Out of Date > Save action takes the view back to package view > ----------------------------------------------- > > Key: TEIIDDES-1253 > URL: https://issues.jboss.org/browse/TEIIDDES-1253 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7 > Reporter: Ramesh Reddy > Priority: Minor > > While working on the transformation view (webservice) a save (ctrl-s) will take the screen all the way back to the package or procedure view, which is annoying if the user has more edit to do. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1284) Usability: Pop-up a warning/notice about needing XA source when multi-source updates are being performed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1284?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1284. ---------------------------------- Resolution: Won't Do > Usability: Pop-up a warning/notice about needing XA source when multi-source updates are being performed > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1284 > URL: https://issues.jboss.org/browse/TEIIDDES-1284 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Van Halbert > Priority: Minor > > When "Supports Update" is checked, it's been requested to pop-up up a message with a warning/notice about needing XA source profiles/connections when multi-source updates are being performed, with maybe a link to: http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Data_Services/5/html/D... > ----- > The Teiid Designer creates a "local" data source by default because of limitations with the JBoss Developer Studio Data Tool. This is not optimal for XA transactions. To create XA datasources, use the JBoss Enterprise SOA Platform Administration Console or use one of the supplied templates for XS data sources in the docs/examples/jca/ directory of the server. > ----- > This is being requested because of the lack of XA datasource support in JBDS data tools. Somehow, the user should be notified that they should an xa datasource and (with the link) know how to do it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1198) Add support for creating partitioned views

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1198?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1198. ---------------------------------- Resolution: Won't Do > Add support for creating partitioned views > ------------------------------------------ > > Key: TEIIDDES-1198 > URL: https://issues.jboss.org/browse/TEIIDDES-1198 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Steven Hawkins > > As an alternative to multi-source models, Teiid supports updatable views defined as union alls that serve the same purpose. It would be good if there was something that could guide the user in creating a partitioned view layer. For example after source A and source B have been imported (of course there could be more than two sources) there could be a modeling option in the new model wizard that creates a view layer not from a single source, but multiple sources. The views would be defined as select 'sourceA' as source_name, ... from sourceA.tbl union all select 'sourceB' as source_name, ... from sourceB.tbl. Obviously without a reconciliation step we would expect tables and column names to match exactly. > Procedures are a special case and don't quite fit cleanly in this approach (or in mulit-source logic either). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1153) Create Model Extension Definition (MED) Compare Editor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1153?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1153. ---------------------------------- Resolution: Won't Do > Create Model Extension Definition (MED) Compare Editor > ------------------------------------------------------ > > Key: TEIIDDES-1153 > URL: https://issues.jboss.org/browse/TEIIDDES-1153 > Project: Teiid Designer > Issue Type: Enhancement > Components: Editors > Affects Versions: 7.6 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: Future > > Attachments: ModelExtensionDefinitionCompareInput.java > > > It is important for a user to know the differences between a MED in the registry and the same MED in the workspace. The MED in the workspace may have changes and the user should be able to see those differences. The compare editor should also be able to compare MEDs that are both in the workspace. When comparing with a registry MED, the registry MED is readonly and cannot be changed by the compare editor. Eclipse has a compare editor framework that should be used. One approach would be to use the built-in text compare editor but having a GUI compare editor might be nicer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1144) Investigate If The Model Extension Definition Validation Done In The Editor Can Be Done Using XSD Validation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1144?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1144. ---------------------------------- Resolution: Won't Do > Investigate If The Model Extension Definition Validation Done In The Editor Can Be Done Using XSD Validation > ------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1144 > URL: https://issues.jboss.org/browse/TEIIDDES-1144 > Project: Teiid Designer > Issue Type: Task > Components: Editors > Affects Versions: 7.6 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: Future > > > The validation being done as the user is editing a MED is done using the ModelExtensionDefinitionValidator (MEDValidator). This validator tries to recreate in code what the MED XSD does when the MED file is parsed. The MEDValidator should use XSD validation libraries to perform validation to guarantee that MED problem markers agree with those reported in the editor. > Looking into this a bit I found that XSD validation libraries only validate entire documents. So to validate just an element value or simple type value does not seem possible. One possible way around this might be to create XML fragments to match the smaller sections of that document that require validation. Research still needs to be done on the feasibility of this idea. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1143) Extension Properties Should Be Shown As Child Elements In the Properties View

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1143?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1143. ---------------------------------- Resolution: Won't Do > Extension Properties Should Be Shown As Child Elements In the Properties View > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1143 > URL: https://issues.jboss.org/browse/TEIIDDES-1143 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 7.6 > Reporter: Dan Florian > Assignee: Mark Drilling > Fix For: Future > > > Currently extension properties are all grouped under the "Extension" category in the properties view. It would be nice if the namespace prefix was nested under "Extension". See the "Button->Size" property example in "http://www.eclipse.org/articles/Article-Properties-View/properties-view.html." > Current Properties View looks like this: > - Extension (opened) > abc:propA | valueA > abc:propB | valueB > abc:propC | valueC > xyz:propX | valueX > xyz:propY | valueY > xyz:propZ | valueZ > The new look in the Properties View could look like this: > - Extension (opened) > + abc namespace (closed) > - xyz namespace (opened) > propX | valueX > propY | valueY > propZ | valueZ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1129) Create IContentOutlinePage Implementation For Model Extension Definition Editor

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1129?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1129. ---------------------------------- Resolution: Won't Do > Create IContentOutlinePage Implementation For Model Extension Definition Editor > ------------------------------------------------------------------------------- > > Key: TEIIDDES-1129 > URL: https://issues.jboss.org/browse/TEIIDDES-1129 > Project: Teiid Designer > Issue Type: Task > Components: Editors, Views > Affects Versions: 7.6 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: Future > > > The outline page view should correspond to the model extension definition (MED) structure and be patterned after Eclipse's Java editor. Selection should be sync'd between the MED editor and the outline view. Actions in the outline should correspond to the appropriate actions in the editor. For instance, if selecting a metaclass in the outline view, two actions could be "Add Extension Property" and "Remove Metaclass." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2017