[
https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin...
]
Barry LaFond commented on TEIID-3140:
-------------------------------------
I don't think so.
Having to look inside the VDB object for specific properties, is simple enough. Currently
in Designer, we're doing that to discover "preview = true". If we even
expose isXmlDeployment() on the VDB, we'd still have to find yet another way/method to
discover whether or not a VDB is a Dynamic VDB ZIP file (containing DDL files).
Teiid supports, out of the box, DEFAULT, PREVIEW, XML, DDL. Exposing a simple TYPE would
clean up the interface and ability for tooling to quickly/easily determine what type of
artifacts are deployed.
I think I understand (a little) that users can use some other metadata type (i.e. replace
DDL). Maybe we add a a 5th type *USERDEFINED* to cover everthing else?
Add getVDBType() method to the VDB interface
--------------------------------------------
Key: TEIID-3140
URL:
https://issues.jboss.org/browse/TEIID-3140
Project: Teiid
Issue Type: Enhancement
Reporter: Barry LaFond
Assignee: Steven Hawkins
Because Teiid supports mutliple VDB types, any tooling designed to interact (edit,
deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly
distinguish what each VDB type is.
Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions
and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata
definitions.
The current VDB interface currently doesn't provide a type.
Request adding something like:
{code}
public enum VDBType {DEFAULT, PREVIEW, XML, DDL}
/**
* @return the vdb type
*/
public VDBType getVDBType();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)