[ https://issues.jboss.org/browse/ARQ-1645?page=com.atlassian.jira.plugin.s... ] Peter Probst edited comment on ARQ-1645 at 3/25/15 3:10 PM: ------------------------------------------------------------ Also it would be perfect if i can bind a @UsingDataset to a @Datasource. So on one method i can have more than one @UsingDataset which have a parameter for the @Datasource to use. Sample: a test method is working on data in multiple schemas, so the data inject would be very easy. Also it would be really great if i can set (optional) a default schema name on @Datasource -> and this schema will be propagated to dbunit. In our case working with postgres it is only possible to use a static schema configuration in arquillian.xml. But this is only valid for one schema. So we now use qualified table names, but then we have to use also schema name in flat xml files -> so these files are not reusable for same schema with different name. The schema name on the @UsingDatasource would solve this problem elegantly. was (Author: peter.probst): Also it would be perfect if i can bind a @Dataset to a @Datasource. So on one method i can have more than one @Dataset which have a parameter for the @Datasource to use. Sample: a test method is working on data in multiple schemas, so the data inject would be very easy. Also it would be really great if i can set (optional) a default schema name on @Datasource -> and this schema will be propagated to dbunit. In our case working with postgres it is only possible to use a static schema configuration in arquillian.xml. But this is only valid for one schema. So we now use qualified table names, but then we have to use also schema name in flat xml files -> so these files are not reusable for same schema with different name. The schema name on the @Datasource would solve this problem elegantly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)