[
https://issues.jboss.org/browse/TEIID-2432?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2432:
-------------------------------------
IMO, I do think we need two states, because from earlier discussions
He was not sure if the VDB was deployed first vs the data source deployed first. We did
not wanted to create that dependency in deployment chain. Even if both configuration went
at same time, or one after the other in right dependency timeline, since AS7 deployment
process being asynchronous we could not depend on, when one is finished, so that other can
start. Thus one of the reason we had the data source not availability as soft error. If we
make that as hard error as single state "FAILED", then there may be some false
deployment errors.
We need some quick way to represent a recoverable error, rather than user looking at model
errors.
Dynamic VDB isLoading state doesnt change on fail
-------------------------------------------------
Key: TEIID-2432
URL:
https://issues.jboss.org/browse/TEIID-2432
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 8.2
Reporter: Mark Drilling
Assignee: Ramesh Reddy
I am deploying a dynamic VDB and polling the isLoading state to determine when the VDB
deployment is finished.
In my case the VDB dataSource is not available. I can see in the server log that the
deployment fails immediately, but the isLoading state remains true.
Is this in error, or what status should we be checking?
--
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