[
https://issues.jboss.org/browse/TEIID-4925?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-4925 at 5/22/17 7:04 PM:
----------------------------------------------------------------
The intent is to wait for that imported VDB to become available - even if it is not yet
deployed. Under normal startup conditions there is no ordering to the deployment of the
vdbs so there could be erroneous messages.
The best resolution would probably be to make sure there was appropriate status
information available to make it clear that the vdb is waiting on other vdbs.
was (Author: shawkins):
We should add an INFO log, but the intent is to wait for that imported VDB to become
available - even if it is not yet deployed.
Importing a non-existing VDB gives no warning
---------------------------------------------
Key: TEIID-4925
URL:
https://issues.jboss.org/browse/TEIID-4925
Project: Teiid
Issue Type: Enhancement
Environment: * Wildfly 10
* Teiid Server 9.2.3
Reporter: Pedro InĂ¡cio
Assignee: Steven Hawkins
Fix For: 9.2.3
Attachments: ReferenceData.png
When importing a "non-existing VDB" in a VDB, when the VDB is deployed, the VDB
status is LOADING, and nothing else happens.
Ideally a warning should be thrown in logs.
Ex:
<code>
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<vdb name="ReferenceDataVDB" version="1">
<description>ReferenceData VDB</description>
<import-vdb name="NonExistingVDB" version="1"/>
<model name="ReferenceData" type="VIRTUAL">
.....
</code>
Logs:
<panel>
12:56:11,529 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2)
WFLYSRV0027: Starting deployment of "ReferenceData-vdb.xml" (runtime-name:
"ReferenceData-vdb.xml")
12:56:11,953 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010:
Deployed "ReferenceData-vdb.xml" (runtime-name :
"ReferenceData-vdb.xml")
</panel>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)