[teiid-issues] [JBoss JIRA] (TEIID-3739) Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-3739:
-------------------------------------

That is by design, imported VDB, could be defined in other VDBs, and materialization caching could have defined, all those needs to be refreshed.

what is the usecase behind 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)