[teiid-issues] [JBoss JIRA] Commented: (TEIID-706) Deployed vdbs should have a consistent unzipped location.

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-706:
------------------------------------

It is my understanding that any configuration changes that are made through admin api, like adding or modifying connector binding will be made on the exploded location, not on the archive. So, that the changes either made manually on the file system or admin api result in the same artifacts always. When you export the VDB using the admin API the resources from the exploded location will be chosen.

> Deployed vdbs should have a consistent unzipped location.
> ---------------------------------------------------------
>
>                 Key: TEIID-706
>                 URL: https://jira.jboss.org/jira/browse/TEIID-706
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Embedded, Query Engine
>    Affects Versions: 6.2.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 6.2.0
>
>
> Deployed vdbs, or vdb less configurationinfo.def files should have a consistent location for their exploded form.  
> Under <teiid home>/deploy there will be folders <vdb name>/<vdb version> - with lower cased names.  On the initial scan for vdbs and def files we will use the corresponding def file to see if the <teiid home>/deploy/<vdb name>/<vdb version> already exists.  If it does not we will create the exploded location, otherwise we'll use it rather than the archive file itself.
> Any changes after deployment time ConfigurationInfo, roles, etc. will only be made to the exploded location.  This will make it easy to document how to modify these files without constantly zipping and unzipping them.
> Ideally this exploded location should also be used by the index file logic rather than using yet another temporary location.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira