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

[Gautam Banerjee (JIRA)]

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

Gautam Banerjee commented on TEIID-1917:
----------------------------------------

Steven,

Here is the code to deploy the VDB from admin api

input.deployVDB(vdbName, ByteStreams.newInputStreamSupplier(vdbString.getBytes()).getInput());

This runs fine when the vdbName is x-vdb.xml and gives exception when i give the vdbName as x.1.vdb.xml

calContainer] 02 Feb 2012 16:50:42,853 IST INFO  [STDOUT] vdbName:chorus.1.vdb.xml
[16:50:42.912][info][talledLocalContainer] 02 Feb 2012 16:50:42,909 IST ERROR [ADMIN_API] Unexpected exception for session W2fAHYi9zSY2
[16:50:42.912][info][talledLocalContainer] [AdminComponentException]The extension of the file name must be either ".vdb" for designer vdb or "xxx-vdb.xml" for dynamic VDBs
[16:50:42.912][info][talledLocalContainer] 1 [AdminProcessingException]The extension of the file name must be either ".vdb" for designer vdb or "xxx-vdb.xml" for dynamic VDBs
[16:50:42.912][info][talledLocalContainer] 	at org.teiid.client.util.ExceptionUtil.convertException(ExceptionUtil.java:72)
[16:50:42.912][info][talledLocalContainer] 	at org.teiid.jboss.deployers.RuntimeEngineDeployer$3.invoke(RuntimeEngineDeployer.java:399)
[16:50:42.912][info][talledLocalContainer] 	at $Proxy312.deployVDB(Unknown Source)

Gautam

 
                
> 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