November 2011 - teiid-designer-issues

[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, 6 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, 6 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, 6 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, 6 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1128) Implement The Model Registry View's Find Reference Action

by Dan Florian (Created) (JIRA)

Implement The Model Registry View's Find Reference Action --------------------------------------------------------- Key: TEIIDDES-1128 URL: https://issues.jboss.org/browse/TEIIDDES-1128 Project: Teiid Designer Issue Type: Task Components: Views Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 8.0 The "Find References" action will find all models that have applied the selected model extension definition. The results of the action should be displayed in Eclipse's search results view. Double-click in the results should open the model. The design of the search results should patterned after the Java->References results. -- 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, 6 months

1
0
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, 6 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1108) Set Query Timeout at the VDB level

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1108?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1108. ------------------------------------ Resolution: Done Added a simple properties group on "Description" tab which is now "VDB Properties" tab. > Set Query Timeout at the VDB level > ---------------------------------- > > Key: TEIIDDES-1108 > URL: https://issues.jboss.org/browse/TEIIDDES-1108 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Environment: Windows > Reporter: RAKESH BALGURI > Assignee: Barry LaFond > Fix For: 7.6 > > > Hi, > We want the configuration of the Query Timeout set on the server side instead of setting it for the Statement Object. > Please see this discussion for more information http://community.jboss.org/message/600599#600599 > We want the setQueryTimeout to override the default values. -- 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, 6 months

1
0
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, 6 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by Barry LaFond (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1010: ----------------------------------- Fix Version/s: 8.0 (was: 7.6) > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-870) We should add a method/dialog to enable users to test JDBC connections used for Teiid instances

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-870?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-870. ----------------------------------- Resolution: Done Added a testJDBCPing() method to our Server class and calling during the ServerPage.handleTestConnection() method. uses dynamic (xml) VDB to deploy/undeploy over admin connection and connecting via JDBC in the middle > We should add a method/dialog to enable users to test JDBC connections used for Teiid instances > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-870 > URL: https://issues.jboss.org/browse/TEIIDDES-870 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dialogs > Affects Versions: 7.3 > Reporter: Len DiMaggio > Assignee: Barry LaFond > Fix For: 7.6 > > > See SOA-2901 - the user cannot test the JDBC connection until after the Teiid instance is first created - but after the user saves the Teiid instance, we should provide a button/dialog to verify the JDBC information that he just entered. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2011