[
https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1822:
-----------------------------------
Fix Version/s: 8.6
(was: 8.5)
Server log still shows ACTIVE and INACTIVE states. Doesn't make sense for Designer to
use different terminology at this time. Pushing to 8.6
Change the way Designer's server framework interprets VDB status
to replace Active/Inactive with isValid() check as Status value
--------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1822
URL:
https://issues.jboss.org/browse/TEIIDDES-1822
Project: Teiid Designer
Issue Type: Task
Components: VDB & Execution
Affects Versions: 8.2
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Minor
Fix For: 8.6
1) Set-up simple JDBC source/model/vdb and test/execute VDB
2) Delete the Data Source in the Server view
3) Try and execute the VDB again and get exception logged in console
Seems the active/inactive status is old terminology and Designer should be using the
isActive() call as well as getValidityErrors() to fine-tune the state of a VDB and prevent
Execute VDB from being launched or at least a warning message check.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira