[
https://issues.jboss.org/browse/TEIID-1917?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1917:
---------------------------------------
Gautam,
I'm not sure another issue is needed just yet. I do not see that exception happening
with that filename - unless you have trailing whitespace or some other oddity not
described by your comment. Again, you need to supply either your code that is using the
adminshell or making direct use of the admin api for better verification. As Ramesh
indicates in his previous comment there does not seem to be any issue with the basic
scenario.
Steve
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