[
https://issues.jboss.org/browse/ARQ-1645?page=com.atlassian.jira.plugin.s...
]
Peter Probst commented on ARQ-1645:
-----------------------------------
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.
persistence doesn't support multiple datasources
------------------------------------------------
Key: ARQ-1645
URL:
https://issues.jboss.org/browse/ARQ-1645
Project: Arquillian
Issue Type: Feature Request
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha6
Reporter: Romain Manni-Bucau
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
It is common to use multiple datsources (in fact all apps I'm working with does it)
and ATM dbunit extension doesn't support multiple datsource init/asserts (UsingDataSet
and ExpectedDataSet).
Would be great to get a plural version of @DataSource and @XDataSet
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)