[
https://issues.jboss.org/browse/TEIIDDES-1822?page=com.atlassian.jira.plu...
]
Barry LaFond edited comment on TEIIDDES-1822 at 8/8/13 4:51 PM:
----------------------------------------------------------------
Our server framework caches the VDB's which are backed by VdbMetadata. Deleting a
data source does not yet result in that cache being updated, hence the VDB's do not
yet show an "INVALID" state.
Refreshing the Server does end up showing invalid (missing data sources) state.
However, recreating the Data Source and refreshing the server does NOT end up with an
"ACTIVE" VDB, it's still INACTIVE
was (Author: blafond):
Our server framework caches the VDB's which are backed by VdbMetadata. Deleting a
data source does not yet result in that cache being updated, hence the VDB's do not
yet show an "INVALID" state.
Refreshing the Server does end up showing invalid (missing data sources) state.
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
Fix For: 8.2.GA
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