[teiid-issues] [JBoss JIRA] (TEIID-1917) Teiid VDB Previous Version not accessible

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Wed Feb 1 09:17:50 EST 2012


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

Steven Hawkins commented on TEIID-1917:
---------------------------------------

Gautam,

Just to make sure, can you provide the commands you are using?  To expand on my previous comment if for example in admin shell you issue deployVDB("x.vdb"), then issue deployVDB("x.vdb") again, the previous version will be undeployed.  The proper versioned usage is to make version part of the filename:
deployVDB("x.1.vdb"), then deployVDB("x.2.vdb")
                
> Teiid VDB Previous Version not accessible
> -----------------------------------------
>
>                 Key: TEIID-1917
>                 URL: https://issues.jboss.org/browse/TEIID-1917
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi
>    Affects Versions: 7.6
>            Reporter: Gautam Banerjee
>            Assignee: Steven Hawkins
>              Labels: Issue, VDB, Version
>
> There can be multiple VDBs of different versions deployed and we can connect to a specific version (documentation says that). But if we connect to a version 1 vdb, then deploy a version 2 vdb of same name, then once the version 2 vdb starts deploying we are not able to connect to version 1 vdb and a meaage comes VDB "Name" version "1" does not exist.
> Am I missing something?

--
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

        


More information about the teiid-issues mailing list