November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Van Halbert (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1149: --------------------------------------- Coping Jeremy Browns comment from SOA-3601: I'd like to add my voice in here to stress how important this is when you have a team working on the same model concurrently. Currently this is not possible but the need for this is really important. > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Assignee: Barry LaFond > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3602 to TEIIDDES-1149: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1149 (was: SOA-3602) Affects Version/s: 7.1.1 7.4.2 (was: JBDS) (was: 5.1.0 GA) (was: 5.2.0.ER6) Component/s: Eclipse Integration Modeling (was: EDS) Security: (was: Public) > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Assignee: Van Halbert > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Van Halbert (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-1149: ------------------------------------- Assignee: Barry LaFond (was: Van Halbert) > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Assignee: Barry LaFond > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1146) There Are Problems Determining If A Model Extension Definition (MED) Applies To Workspace Selection

by Dan Florian (Created) (JIRA)

There Are Problems Determining If A Model Extension Definition (MED) Applies To Workspace Selection --------------------------------------------------------------------------------------------------- Key: TEIIDDES-1146 URL: https://issues.jboss.org/browse/TEIIDDES-1146 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Priority: Blocker Fix For: 7.6 MED-related actions need to be able to determine if a MED is applicable for their certain situation. For instance, determining if a MED can be added to a selected model. Currently the MED only knows the metamodel URI that it extends and what metaclasses it extends. It does not know anything about model type (physical or virtual). Should the MED also include the model type? Or should the ModelExtensionAssistant be responsible for determining the applicability of it's MED given a certain situation. Here are 2 scenarios that are causing a problem: 1. The Model MED management dialog is not showing for XML Doc models and should be. 2. The REST MED can be added to non-virtual models. -- 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

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1080) Validate Salesforce URL when creating a connection profile

by Mark Drilling (JIRA)

Validate Salesforce URL when creating a connection profile ---------------------------------------------------------- Key: TEIIDDES-1080 URL: https://issues.jboss.org/browse/TEIIDDES-1080 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 7.6 Recommend validate the URL form before connection to Salesforce. Salesforce provides a regex to validate - at http://wiki.developerforce.com/index.php/Requirements_Checklist -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-186) NoClassDefFoundError issues when importing JDBC data source

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-186?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-186. ----------------------------------- Assignee: Barry LaFond Resolution: Cannot Reproduce Bug no recent problems, can't reproduce > NoClassDefFoundError issues when importing JDBC data source > ------------------------------------------------------------ > > Key: TEIIDDES-186 > URL: https://issues.jboss.org/browse/TEIIDDES-186 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: eclipse.buildId=I20090430-2300 > java.version=1.6.0_07 > java.vendor=Apple Inc. > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -keyring /Users/btruitt/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/btruitt/.eclipse_keyring -showlocation > This is a continuation of log file /Users/btruitt/workspace/.metadata/.bak_0.log > Created Time: 2009-05-12 15:43:45.985 > teiid_designer_6.0.0.v20090427_SNAPSHOT > Reporter: Ben Truitt > Assignee: Barry LaFond > Fix For: Future > > Attachments: stack_trace_1.rtf, stack_trace_2.rtf, stack_trace_3.rtf, stack_trace_4.rtf, stack_trace_5.rtf, stack_trace_6.rtf, stack_trace_7.rtf, stack_trace_8.rtf > > > When I try to import from a Postgresql 8.2 database using postgresql-8.3-604.jdbc4.jar on eclipse 3.5 M7, teiid_designer_6.0.0.v20090427_SNAPSHOT, on mac os x with java 1.6 64-bit, I get the attached stack traces. > Several NoClassDefFoundError errors occur. > After that, the generated model is reported as being in error. Note, when I import a view from the same database, I do not get this problem. Based on the errors that are reported in the generated model, it seems to be caused by references to foriegn keys and indices, etc. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-160) Retain log level settings across executions of a VDB.

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-160?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-160. ----------------------------------- Resolution: Out of Date VDB Editor no longer exposes log levels > Retain log level settings across executions of a VDB. > ----------------------------------------------------- > > Key: TEIIDDES-160 > URL: https://issues.jboss.org/browse/TEIIDDES-160 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > Fix For: No Future > > > VDB execution sessions always start with the default logging level. If you change the level and close the connection, the change is lost and the next invocation again starts with default level. This makes it impossible to start a session in anything other than default level. Starting a connector in a richer logging level is helpful when trying to debug connector startup. > You can accomplish this currently by editing the config.xml. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-159) Designer log levels do not map to code level log levels.

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-159?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-159. ----------------------------------- Resolution: Out of Date VDB Editor no long exposes Log levels > Designer log levels do not map to code level log levels. > -------------------------------------------------------- > > Key: TEIIDDES-159 > URL: https://issues.jboss.org/browse/TEIIDDES-159 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Reporter: John Doyle > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > When testing VDB's you have the option to set the logging level, but the names of the level do not map correctly to the API level log calls. For instance, the "Trace" level in the designer UI actually logs Info level messages. Also, there is no way to get to a more detailed level in the UI. Perhaps we should also offer all levels, rather than three. -- 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

14 years, 5 months

1
0
0 / 0

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

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-84?page=com.atlassian.jira.plugi... ] Barry LaFond resolved TEIIDDES-84. ---------------------------------- Resolution: Out of Date Description view editing has changed so this problem goes away. > Description View And Transformation Editor Background Color Does Not Update When Changing Resource Readonly State Until Workspace Selection > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-84 > URL: https://issues.jboss.org/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: Future > > > 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, 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-82) Make creating custom diagrams and diagram object addition/deletion UNDO-able events

by Barry LaFond (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-82?page=com.atlassian.jira.plugi... ] Barry LaFond updated TEIIDDES-82: --------------------------------- Fix Version/s: No Future (was: Future) > Make creating custom diagrams and diagram object addition/deletion UNDO-able events > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-82 > URL: https://issues.jboss.org/browse/TEIIDDES-82 > Project: Teiid Designer > Issue Type: Task > Components: Diagrams > Affects Versions: 6.0.0 > Environment: All > Reporter: Paul Nittel > Fix For: No Future > > > Make creation of custom diagrams an UNDO-able event. Also, make the addition of and deletion of objects (in custom diagrams) UNDO-able events, too. > Defect 13599 was the genesis of this. -- 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

14 years, 5 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 November 2011