[
https://issues.jboss.org/browse/TEIID-3739?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3739:
---------------------------------------
Having a hard dependency on the imported vdb triggers the imported vdb service removal.
Once the new imported vdb is available though nothing triggers the importing vdb service
to restart. It looks like redeploying a translator would have the same effect - all vdbs
that use it would need to be redeployed. Ramesh - should the importing vdb service not be
removed when an import is removed (and have additional active/inactive handling for this),
or does this seem like an EAP issue?
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)