[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] 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. -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] Gautam Banerjee commented on TEIID-1917: ---------------------------------------- I did not choose any connection type. It is default. -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1917: ------------------------------------- I tried with latest Teiid, and used explicit version convention in the URL like jdbc:teiid:vdb.1@mm://localhost:31000 from adminshell was successful connecting to both versions deployed. -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1917: ------------------------------------- That is a separate issue, just rename both files uniquely and deploy and connect for your testing. you can open another issue for this. -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] 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 -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] Gautam Banerjee commented on TEIID-1917: ---------------------------------------- Thanks! I am able to connect multiple version vdb. The correct name is x.1-vdb.xml. The documentation should be updated. I have a related query. Once the latest version is deployed then how long will the previous version vdbs be available. Will they timeout and undeploy themselves or exist as long as there is some connection on it. -- 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

[ https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1917: ------------------------------------- For doc see http://docs.jboss.org/teiid/7.6.0.Final/reference/en-US/html_single/#dyna... it does say about the name pattern There is no timeouts, the VDB will be in deployed form until it is explicitly undeployed. -- 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