[
https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3739:
-------------------------------------
When the dependency comes back, the original service that depends on it gets restarted
again. So, in this case when the imported VDB comes back active, then the importing VDB
should follow that, unless we configured as optional dependency.
Dynamic VDB that imports another VDB does not get redeployed if the
imported VDB is redeployed
----------------------------------------------------------------------------------------------
Key: TEIID-3739
URL:
https://issues.jboss.org/browse/TEIID-3739
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.7.1.6_2
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Attachments: dynovdb1-vdb.xml, dynovdb2-vdb.xml
When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported
VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but
only redeploys the imported one. The top VDB then doesn't exist until it's
redeployed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)