October 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1008) Search Transformations Dialog in Designer has layout issues

by Mark Drilling (JIRA)

Search Transformations Dialog in Designer has layout issues ----------------------------------------------------------- Key: TEIIDDES-1008 URL: https://issues.jboss.org/browse/TEIIDDES-1008 Project: Teiid Designer Issue Type: Enhancement Components: Dialogs Affects Versions: 7.1.1 Reporter: Mark Drilling Priority: Minor After doing a 'Perform Search' in the Dialog, the search results are populated into the center text area - and the dialog components are proportioned reasonably. However, any re-size of the dialog (after results are populated) causes the results area to re-size - covering up the lower SQL area. The dialog layout should be adjusted so that re-size doesn't cover up the SQL area. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1007) Metadata Search page does not take into account the Scope Selection

by Mark Drilling (JIRA)

Metadata Search page does not take into account the Scope Selection ------------------------------------------------------------------- Key: TEIIDDES-1007 URL: https://issues.jboss.org/browse/TEIIDDES-1007 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 7.1.1 Reporter: Mark Drilling Priority: Minor The Metadata Search Wizard ignores the "Scope" selection - it always searches the entire workspace. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
6
0 / 0

[JBoss JIRA] (TEIIDDES-1096) 'Add Models' button in VDB editor appears to be disabled

by Randall Hauch (Created) (JIRA)

'Add Models' button in VDB editor appears to be disabled -------------------------------------------------------- Key: TEIIDDES-1096 URL: https://issues.jboss.org/browse/TEIIDDES-1096 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.4 Environment: OS X 64-bit Reporter: Randall Hauch Attachments: VDB editor add model button.png The add models button in the VDB editor appears to be disabled. Perhaps the image/icon is just similar enough to other disabled icons that it just appears that way. -- 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

12 years, 7 months

5
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-905) Replace EMF-based Model Extensions with new framework

by Barry LaFond (JIRA)

Replace EMF-based Model Extensions with new framework ----------------------------------------------------- Key: TEIIDDES-905 URL: https://issues.jboss.org/browse/TEIIDDES-905 Project: Teiid Designer Issue Type: Enhancement Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 Designer's current Model Extensions framework has some limitations which include: 1. The current framework allows for only 1 extension model. 2. Extension models are included as a dependent models in VDBs. 3. When sequenced through publishing into the Modeshape repository none of the default "extended" property values are currently sequenced. There is no mechanism in Modeshape to associate 2 or more documents in this way. 4. When using the EMF Extension Model, EMF controls when Annotation objects are created, and we're creating annotation objects even when none are strictly needed (e.g., all the tags in the annotation have default values, and thus don't appear in the XMI file). The result is a lot of unnecessary Annotation objects. Need to design a new framework that is scalable, allows for applying multiple extensions, includes the extension metadata within a model (initial values and types) and can be easily adapted/sequenced by Modeshape. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1073) Create Extension Point And Metamodel Plugin Extensions For Those Metamodels Which Are Allowed To Have Model Extension Properties

by Dan Florian (JIRA)

Create Extension Point And Metamodel Plugin Extensions For Those Metamodels Which Are Allowed To Have Model Extension Properties --------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1073 URL: https://issues.jboss.org/browse/TEIIDDES-1073 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.5 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.6 An extension point should be created in org.teiid.designer.extension that permits metamodel plugins to indicate their metamodel can be extended using the model extension framework. Extensions for each metamodel plugin that can be extended should also be written. This extension point should be loaded by the ExtensionPlugin at startup. The ExtensionPlugin should then register these metamodels with the ModelExtensionRegistry. The registry should add supporting method(s) required by the framework. For instance, when creating or validating a ModelExtensionDefinition (MED), the MED's extended metamodel should be checked to make sure it is authorized to be extended. An existing extension point is used for registering MEDs at startup. This new extension point should be loaded first so that the extended metamodel can be checked when registering/creating the built-in MEDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1075) Create Model Resource UI Action To Manage Model Model Extension Definitions (MEDs).

by Dan Florian (JIRA)

Create Model Resource UI Action To Manage Model Model Extension Definitions (MEDs). ----------------------------------------------------------------------------------- Key: TEIIDDES-1075 URL: https://issues.jboss.org/browse/TEIIDDES-1075 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 7.5 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.6 Create a model resource context menu action that will provide the user the ability to manage the selected model's stored MEDs. The action should only be enabled when one model is selected and should appear in the "Modeling" submenu. The UI should provide the ability to add to/store those applicable MEDs (i.e., MEDs that extend the same metamodel of the selected model) that are not currently being stored in the model. The UI should also allow the user to remove MEDs from model that are currently stored in the model. Also the UI should: - provide an option to register any stored, unregistered MED to the registry (just need path from user), - show a dialog informing the user there are no MEDs saved in the model and none that can be applied based on the model's metamodel URI, - inform the user when removing a MED that all associated MED model object extension properties will also be deleted, and - show the user which stored MEDs in model are not registered or if the versions are different -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1115) The Model Extension Registry Should Be Persisted At Shutdown And Restored At Startup

by Dan Florian (Created) (JIRA)

The Model Extension Registry Should Be Persisted At Shutdown And Restored At Startup ------------------------------------------------------------------------------------ Key: TEIIDDES-1115 URL: https://issues.jboss.org/browse/TEIIDDES-1115 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 7.6 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.6 The model extension registry needs to be persisted in the extension plugin's state location under the .metadata folder. Using an Eclipse linked resource for the exact location should be investigated as one day this location could exist outside the workspace. The ExtensionPlugin should persist the registry at shutdown and restore the registry at startup. Only user-defined (non-built-in) model extension definitions (MEDs) need to be persisted as the built-in MEDs can continue to be loaded into the registry using the existing extension point. Two possible ways of persisting the registry would be (1) create/save *.mxd file for each registered MED, or (2) create one *.xml file that contains entries for each registered MED. Advantage of (1) is that at startup the existing way of reading and writing MEDs could be used. Advantage of (2) would be only one file would be needed. The existing MED writer could potentially be modified for use in (2). See the DqpPlugin as it is solving a similar problem. -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1116) Model Extension Definition (MED) Editor Should Show The Available Extendable Metaclass Names

by Dan Florian (Created) (JIRA)

Model Extension Definition (MED) Editor Should Show The Available Extendable Metaclass Names -------------------------------------------------------------------------------------------- Key: TEIIDDES-1116 URL: https://issues.jboss.org/browse/TEIIDDES-1116 Project: Teiid Designer Issue Type: Sub-task Components: Editors Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 The MED editor currently requires the user to type in the fully qualified Java class name of the metaclass being extended. The editor should instead provide a set of all available metaclass names to the user to choose from. This is the way the extension model framework being replaced worked. Since metaclasses can have containment associations those relationships should be shown in a tree form. One way of providing these metaclass names would be to add the requirement to the extension point that identifies the extendable metamodels. For instance, each extension could provide an instance of interface that has a method like "getExtendableMetaclasses()." The editors metaclass dialog would need to be changed to provide a Tree UI object to choose the metaclass name. -- 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

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1074) Create New Model Extension Definition Wizard

by Dan Florian (JIRA)

Create New Model Extension Definition Wizard -------------------------------------------- Key: TEIIDDES-1074 URL: https://issues.jboss.org/browse/TEIIDDES-1074 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 7.5 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.6 Create a wizard that allows the user to create a new Model Extension Definition (MED). The wizard should be an extension of the "org.eclipse.ui.newWizards" extension point and should be located in the "org.teiid.designer.extension.ui" plugin. The information required by the wizard is name of the "*.mxd" file, the workspace folder to put the "*.mxd" file, the namespace prefix of the MED, and the namespace URI of the MED. If the namespace prefix or namespace URI is already registered in the ModelExtensionRegistry the UI should warn the user but not prevent them from creating the MED. When all required information is entered in the UI the wizard should open the MED Eclipse editor. The wizard should not register this new MED in the registry. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1077) Create A Model Extension Definition (MED) Eclipse Editor

by Dan Florian (JIRA)

Create A Model Extension Definition (MED) Eclipse Editor -------------------------------------------------------- Key: TEIIDDES-1077 URL: https://issues.jboss.org/browse/TEIIDDES-1077 Project: Teiid Designer Issue Type: Sub-task Components: Editors Affects Versions: 7.5 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 Create a GUI MED editor using Eclipse resource editor framework. This editor be used to edit "*.mxd" files. In addition, this editor should: - not allow editing of readonly *.mxd files - inform user of implications of changing MED (could result in deletion of model object properties) - should saving the new MXD editor add to the registry or should there be "Add to registry" button? - should allow "Save As" - "Save" should validate using the MED parser and registry methods - "Save" should NOT automatically update registry (which causes side-effects). Should have another way of updating registry. Stretch goals: - change to a multi-tabbed editor that would add a "Source" or textual view of MXD file - support for the Eclipse Outline View - support the MXD content that has i18n features -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2011