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

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Tue Jan 31 15:16:48 EST 2012


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

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

Also the logged component was admin api.  If this is the case, please provide the sequence of commands to reproduce the issue.

Be sure to clarify what is meant by "same name".  If a file deployment or he admin api deployVDB filename is the same as an existing vdb artifact, then the previous will be effectively removed by the new deployment.
                
> 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