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