September 2011 - teiid-designer-issues

[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] 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

[JBoss JIRA] Created: (TEIIDDES-1076) Create Model Extension Registry Eclipse View

by Dan Florian (JIRA)

Create Model Extension Registry Eclipse View -------------------------------------------- Key: TEIIDDES-1076 URL: https://issues.jboss.org/browse/TEIIDDES-1076 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 7.5 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.6 Create an Eclipse View that shows the current state of the Model Extension Registry (MER). The MER is where all Model Extension Definitions (MEDs) and all extendable metamodel identifiers are stored. Since there will be soon be an Eclipse editor for MEDs this registry view does not need to show all details of every MED. At a minimum the view should show for each MED the namespace prefix, namespace URI, metamodel URI, version, if it is built-in or user-defined, and description. In addition the UI should: - include a way to add/register a MED to the registry. Users should be able to add a MED by either (1) selecting existing workspace MXD file (MED must be valid), or (2) selecting non-workspace MXD file which will add to the file to the workspace and to registry. - include a way to delete a single MED from the registry (refactor). Ask user if they also want that MED deleted from all models that are storing it. Warn user the deleting MED from model will also delete any associated model object properties. Deleting a user-defined MED from the registry should not automatically delete MXD file from the workspace unless confirmed by user. - include a way to open the MED Eclipse editor for a selected model(s). Warn user that changes can affect models in the workspace. Ask if changes made to MED should be applied to all models that have been storing that MED (this maybe an MED editor requirement). A double-click should also open the MED editor. - include a way to find workspace models storing the single selected MED. Results should be stored using Eclipse's Search results view. - should only allow one version of MED in the registry (make sure registry is doing this) -- 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-1053) Create XML View Documents refers to XML Message Structure in wizard

by Barry LaFond (JIRA)

Create XML View Documents refers to XML Message Structure in wizard ------------------------------------------------------------------- Key: TEIIDDES-1053 URL: https://issues.jboss.org/browse/TEIIDDES-1053 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Minor Fix For: 7.6 The XML Document Builder page for the Modeling > Create XML View Documents (selected a schema Element) is titled Build XML Message Structure.... Needs to be Build XML Documents .... Also need to remove all the old XML Message Structure UI components. This action wrongly uses the message structure gui. Need to convert to use same as with XML Document New Model Wizard -- 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-993) Add package diagram for webservices that shows the relationships between the different artifacts

by Van Halbert (JIRA)

Add package diagram for webservices that shows the relationships between the different artifacts ------------------------------------------------------------------------------------------------ Key: TEIIDDES-993 URL: https://issues.jboss.org/browse/TEIIDDES-993 Project: Teiid Designer Issue Type: Enhancement Components: Diagrams Affects Versions: 7.5 Reporter: Van Halbert For webservices, provide a package diagram that shows what the relationships are for a given webservice. This would be very useful to help visualize all the parts and their relationship to creating the webservice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1021) Apply 7.5 bug fixes to 7.4.2 branch

by Barry LaFond (JIRA)

Apply 7.5 bug fixes to 7.4.2 branch ----------------------------------- Key: TEIIDDES-1021 URL: https://issues.jboss.org/browse/TEIIDDES-1021 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 7.4.2 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4.2 7.5 OPEN JIRA candidates TEIIDDES-603 Change Generated CXF WAR and REST WAR to create Dynamic Web Projects TEIIDDES-958 Provide a way for the user to see the Teiid SQL Grammer reserved words TEIIDDES-963 Add jboss tools runtime detector for Teid Servers TEIIDDES-965 Add option to generate a war with MTOM support TEIIDDES-983 Add Export Option for Generated SOAP and REST Wars TEIIDDES-987 Add ability to edit/generate Create Virtual Procedure SQL statements for RestEasy XML, File and Web Service Translator procedures TEIIDDES-992 Allow the use of pushdown functions without requiring Java programming TEIIDDES-1016 Reduce the Relationship metamodel UI contirbutions to bare minimum for displaying legacy relationship models COMPLETED in 7.5 (Most are not large fixes) ====== UI Upgrades ========== TEIIDDES-981 Preview Data Action Should Let User Know When There Is Not A Default Teiid Instance Defined TEIIDDES-340 Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard TEIIDDES-972 When importing an existing model, message notes that this is an existing model but 'Update' is not chosen by default TEIIDDES-990 Add JSON Support to Generated REST War TEIIDDES-369 Designer: Annotate objects that are 'pre-viewable' TEIIDDES-332 New virtual procedures should always contain the prologue/postlogue, rather than require the user to remember the syntax -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
20
0 / 0

[JBoss JIRA] Created: (TEIIDDES-620) Add Option for Embedded Teiid Connection vs JNDI in WAR Generation

by Ted Jones (JIRA)

Add Option for Embedded Teiid Connection vs JNDI in WAR Generation ------------------------------------------------------------------ Key: TEIIDDES-620 URL: https://jira.jboss.org/browse/TEIIDDES-620 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to allow for a embedded Teiid connection in the war generation process in addition to the current JNDI connection. This is required for HTTPBasic support. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1048) ModelExtensionAssistant API Should Be Changed To Remove Methods That Pertain To Namespaces Other Than Their Own

by Dan Florian (JIRA)

ModelExtensionAssistant API Should Be Changed To Remove Methods That Pertain To Namespaces Other Than Their Own --------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1048 URL: https://issues.jboss.org/browse/TEIIDDES-1048 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.4 Reporter: Dan Florian Assignee: Mark Drilling Fix For: 7.5 A ModelExtensionAssistant pertains to one specific namespace yet has methods that have parameters that take a namespace or have methods that return data gathered with knowledge of other namespaces. This abstract class API should be changed to remove methods like this. For instance, the "supports(Object, String)" method takes a namespace prefix as the second parameter. This second parameter should be deleted as an assistant knows its own namespace prefix. Also the method "getSupportedNamespaces(Object)" should be deleted. An assistant should only be responsible for knowing if its own namespace is supported by a model object. All methods in the API should be checked for similar issues. And all subclasses should be checked to make sure similar issues aren't present. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2011