[teiid-issues] [JBoss JIRA] (TEIID-2310) VDB import issues

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-2310.
---------------------------------

        Labels: final  (was: )
    Resolution: Done


Service unloading for switch service which is dependent service was uneven, thus it was not reloading.

Also copied the vdb-imports to the composite vdb, when it is built.
                
> VDB import issues
> -----------------
>
>                 Key: TEIID-2310
>                 URL: https://issues.jboss.org/browse/TEIID-2310
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.1
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>              Labels: final
>             Fix For: 8.2
>
>
> During the vdb-import testing found couple issues
> 1) VDB-Import information is not available, when a vdb that has vdb-import defined, and queried through CLI or Teiid Console, Admin Shell.
> 2) VDB is not properly re-loading, when dependent VDB has been re-deployed. For example, if we have 3 vdbs
> PartsTop_VDB.vdb -> imports -> PartsCommon_View.vdb -> imports -> PartsCommon_Root.vdb
> then if we do deploy of all the vdbs in any order, we will have all the 3 VDBS available in server. Then if you, undeploy
> undeploy PartsCommon_View.vdb
> then it will remove "PartsCommon_View.vdb" and also "PartsTop_VDB.vdb" as it depends on it. 
> However, upon re-deployment of "PartsCommon_View.vdb" the "PartsTop_VDB.vdb" should come up with out any issues, but it does not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira