[teiid-issues] [JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-5394:
---------------------------------------

> I was thinking to load each VDB file then, using MetadataFactory write back a single VDB out.
 
If you are suggesting to do that at runtime, that's not much different than what I'm suggesting.

> Even otherwise, I think we can/should impose rules how vdb-import works, like it must have separate ddl files etc, as it is an advanced feature.

The components of a vdb for vdb import purposes are:

main .xml or .ddl - containing schema, translator, and optional role information
schema ddl and secondary artifacts
yaml configuration

Are you thinking we would restrict the import to only the schema ddl?  Seems like that will require the redefinition of a lot of the other possible information.

> The yaml files are not part of the VDB artifact.

You may want to alter the current behavior.  See the .vdb from rdbms-as-datasource, it will contain the yaml as described above.

Also a .ddl file is not covered by the maven plugin logic.  Was that intentional?

> Define how to utilize multiple vdbs
> -----------------------------------
>
>                 Key: TEIID-5394
>                 URL: https://issues.jboss.org/browse/TEIID-5394
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Build/Kits
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 11.1
>
>
> Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)