[teiid-issues] [JBoss JIRA] (TEIID-2021) Fail the VDB deployment when translator is not available

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-2021:
-------------------------------------

Once the service starts, the deployment would have been finished. So, even throwing the StartException the user need to undeploy and re-deploy the VDB. By stopping at deployment, the undeploy is not required.

The code always assumed that the translators were already been deployed, so that we can associate connector managers at VDBService start with vdb service. Treating them as data sources, where they are loosely coupled can be done, but that needs to more work.

Currently when a translator is removed, the vdbs that depend on it stopped, and once they are available then the service starts again.
                
> Fail the VDB deployment when translator is not available
> --------------------------------------------------------
>
>                 Key: TEIID-2021
>                 URL: https://issues.jboss.org/browse/TEIID-2021
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 8.0
>
>
> VDBDeployer checks for the override translator types, however it does not check for the base translators that are configured in the VDB. So, when a VDB with unknown translator is deployed, it gets deployed but never exposes any error information as to why the VDB is not "active".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira