]
Ramesh Reddy commented on TEIID-1710:
-------------------------------------
so what is the suggestions here? I do not think listing all the valid databases is good
idea. We can it does not exist, so check your vdb name?
Request better exception message when connecting to an invalid VDB
name
-----------------------------------------------------------------------
Key: TEIID-1710
URL:
https://issues.jboss.org/browse/TEIID-1710
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.1.1
Reporter: Debbie Steigner
Assignee: Van Halbert
When accessing a VDB with the incorrect name (in my case, a typo), the exception suggests
that it's either down to an invalid logon and/or access problems. This is mis-leading
and time-consuming to track down:
09:52:35,991 WARN [SECURITY] Processing exception 'VDB "XXX" version
"latest" does not exist.' for session null. Exception type
org.teiid.client.security.LogonException thrown from
org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:228). Enable
more detailed logging to see the entire stacktrace.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: