August 2011 - teiid-designer-issues

[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

14 years

4
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

14 years

3
8
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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-992) Allow the use of pushdown functions without requiring Java programming

by Bernd Groh (JIRA)

Allow the use of pushdown functions without requiring Java programming ---------------------------------------------------------------------- Key: TEIIDDES-992 URL: https://issues.jboss.org/browse/TEIIDDES-992 Project: Teiid Designer Issue Type: Feature Request Reporter: Bernd Groh Currently, in order to use a database function, even if pushdown is required, it is still necessary to add the function interface to a Java class within the connector, and the connector then must be deployed to the server in order to allow for this pushdown function to be used within the Designer. This creates a lot of extra effort every time you want to make use of a new database function. Particularly, given the schema designer doesn't necessarily have access to either the connector code or the server, and then must involve other parties simply to be able to use an additional database function. It would be very beneficial to speedy schema development if that was not necessary, and if, say, the interface could be defined on the Designer side, added to the VDB, and then deployed as part of the VDB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
47
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1006) Get NPE upon attempt to set description on a mapping class diagram in ModelExplorer

by Mark Drilling (JIRA)

Get NPE upon attempt to set description on a mapping class diagram in ModelExplorer ----------------------------------------------------------------------------------- Key: TEIIDDES-1006 URL: https://issues.jboss.org/browse/TEIIDDES-1006 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Environment: Fedora 14, x64 JBDS 4.0.1 Reporter: Mark Drilling Priority: Minor Attempt to set description text on a MappingDiagram object (the tab text box is editable) in ModelExplorer results in the attached NPE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-936) Version 7.5 Release Work

by Barry LaFond (JIRA)

Version 7.5 Release Work ------------------------ Key: TEIIDDES-936 URL: https://issues.jboss.org/browse/TEIIDDES-936 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.5 All general work related to releasing 7.5 Starts with upgrading Trunk feature.xml, MANIFEST.MF and pom.xml files to 7.5 qualifier -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2011