[teiid-issues] [JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006164#comment-13006164 ] 

Steven Hawkins commented on TEIID-3140:
---------------------------------------

Van that's not in scope.  It will be quite sometime before all of a vdb is expressible as DDL.  And there are slightly different concerns.  There is the question of what is the runtime metadata (which as you point out can include details of the vdb itself) and there's the notion of the deployment artifact - which necessarily has to know what metadata repositories / ddl files / vdb details.

What Barry is trying to do is neatly categorize the VDBs, but what we're saying is that we don't make that many distinctions.  We have either an xml or a zip deployment and then it's up to the details of the vdb as to how the metadata is loaded.

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