[ https://issues.jboss.org/browse/TEIIDSB-127?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIIDSB-127: ---------------------------------------- Closed the pr to move the discussion over here. Here's what I've tried: Order on the configuration and datasource beans - this does not work as it's for ordering in a collection. Lazy, PriorityOrder, AutoConfigurationOrder also did not work. The ApplicationContext (shown in the pr) or an approach using AutoWire of source lists with a qualifier (to exclude the Teiid DataSource) works for as long as there's no spring data initialization. But the creation of the Teiid DataSource can happen in between the creation of the other source and when spring runs the schema creation - thus the test failure with the pr. The only thing that seems to consistently work is an explicit depends on. In the DataSources class if we require something like: {code} @DependsOn("mydb", "myotherdb",...) public Object sources() { return new Object(); } {code} Then add an {code} @DependsOn("teiid-sources") {code} To our DataSource then spring can figure it all out. I'm not sure if there is a great way to turn that into a configuration property as DependsOn expects an array, not a comma separated list. An issue would probably be the handling of multiple DataSources classes. I'll try playing around with some of the Conditional annotations, but beyond that I'm out of ideas. As long as the vdb is not importing from a source to define the metadata it is possible to work around this particular issue by adding more logic to the transaction management initialization such that it can allow more datasources to be added later - but of course that's not a general solution to this problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)