Bug 780480 (SOA-2908)

Summary: Deploying VDB XML file before data sources leads to failed deployment
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Paul Nittel <pnittel>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.CR1CC: vhalbert
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2908
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-24 18:30:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Paul Nittel 2011-02-14 16:49:38 UTC 
Workaround Description: Copy the file with the data source first (or simultaneously), or restart the server.
project_key: SOA

Using the dynamic portfolio example, the readme instructs the user to:

Copy the following files to the <jboss.home>/server/default/deploy directory.
	- portfolio-vdb.xml
	- marketdata-file-ds.xml

If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens.

The VDB deploys (inactive state)
The data source deploys successfully
The VDB status changes to active.

Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked.

Issues at play are:
1) The readme's copying instructions are backwards, and
2) The VDB is marked as active when it should not be

Both should be corrected.
Comment 1 Van Halbert 2011-02-14 18:18:32 UTC 
There is actually a bug in Teiid that's results in having to deploy the datasoure(s) prior to deploying the dynamic vdb.   Until the bug is fixed, the user will need to deploy the files in the specified order (i.e., first, datasources, then the -vdb.xml file).
Comment 2 Van Halbert 2011-02-14 18:18:48 UTC 
Link: Added: This issue Cloned to SOA-2909
Comment 3 Van Halbert 2011-02-24 18:29:17 UTC 
Link: Added: This issue is related to SOA-2844