[
https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu...
]
Van Halbert commented on TEIIDDES-2401:
---------------------------------------
I would like to see Teiid, after having a VDB updated via CLI, to have the VDB saved to
the filesystem in a format such that it can be redeployed. Because, right now, if a VDB
is changed via CLI, there's no way to get that VDB out so that it can be redeployed on
another server.
In an ideal world, Teiid would persist the changed VDB to the filesystem, so that when an
API method is called to get VDB, the current state of the VDB is returned in a form that
can be deployed to another server.
Add support exporting the Designer VDB as Dynamic VDB
-----------------------------------------------------
Key: TEIIDDES-2401
URL:
https://issues.jboss.org/browse/TEIIDDES-2401
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Reporter: Ramesh Reddy
When a VDB is developed in the Designer, provide an option to export the given VDB as
Dynamic VDB, which is simple XML format using DDL.
The server already provides mechanism to retrieve the schema (DDL) for a given model.
Using this technique of retrieving the DDL, this feature can be built.
One caveat is support for XML document models in Dynamic VDB. When VDB contains XML
document model, do not support this feature.
This has couple benefits
* Users can use these in Teiid for simplified usage.
* Can used to check the models into source repository like GIT or SVN etc and compare
with later versions for modifications
* Open Shift
As for importing of Dynamic VDB, that can be handled as separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)