[
https://issues.jboss.org/browse/TEIIDDES-1508?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1508:
----------------------------------------
As a minimum, Designer VDBs contain vdb.xml (manifest), XMI files and their corresponding
Index files (metadata consumed by Teiid). To generate the index files requires EMF and
Designer's validation framework.
Exposing this capability through an API would not be a small task, but should be doable.
Add ability to Build a EDS VDB via APIe
---------------------------------------
Key: TEIIDDES-1508
URL:
https://issues.jboss.org/browse/TEIIDDES-1508
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Ability to build a VDB pro-grammatically via an API
The need is to build the VDB during their build process, so would like to pull XMI's
into the build process, then bind them together into a VDB for release. This way the
build process can choose which version of the XMI files to bundle together into the VDB.
Also an addition to this, it would be (almost necessary) great to be able to define what
goes into the VDB (roles, translators to use, translator overrides etc) in a file that we
can provide to the API, and also that we can check in to our source control.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira