[
https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3140:
-------------------------------------
The designation is based on file type or metadata type? File type is environment specific
detail whether it XML or .ZIP file, and there are many metadata types, NATIVE, DDL,
.INDEX, USERDEFINED etc.
If you are looking for file designation, isXMLDeployment should be sufficient. If you are
looking for metadata designation each model can be different, it needs to handled
differently. I do not even think we track this currently as everything is just metadata.
Increasingly most of the Dynamic VDB model metadata can be generated from multiple
different metadata repos, like NATIVE and DDL. What we call that?
BTW, PREVIEW is designation that Designer gave, runtime has no knowledge of it is just a
custom property, there is no XML. DEFAULT is .INDEX files.
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)