[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5394:
-------------------------------------
The drawback to the build time approach is that it's not
straight-forward to flatten vdb.xml nor vdb.ddl contents. It's only straight-forward
to flatten on a per schema >basis when those are captured as separate ddl files.
I was thinking to load each VDB file then, using MetadataFactory write back a single VDB
out. 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.
From the teiid thorntail examples the project yaml is treated as a
resource that is copied into the target/classes, which is then picked up by the vdb maven
>plugin for inclusion in the .vdb. Is that not what you had in mind?
The yaml files are not part of the VDB artifact. There are two maven plugins at play
there, one is VDB maven plugin that takes the VDB files and builds an archive artifact,
another is Thorntail deployment/Uber jar plugin which picks up the main artifact of the
project along with yaml files and builds an Uber Jar that is executable. If this Uber Jar
needs to deploy into OpenShift, then third FMP plugin which does the docker wrapping and
OpenShift specific configuration which is separate from Thorntail configuration.
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)