Bartosz Majsak created ARQ-771:
----------------------------------
Summary: Global DBUnit configuration should be exposed in arquillian.xml
Key: ARQ-771
URL:
https://issues.jboss.org/browse/ARQ-771
Project: Arquillian
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
Use arquillian.xml with dedicated qualifier such as "persistence-dbunit" and
handle it in the same fashion as currently available properties for the extension
(preferably in dbunit package):
* Create configuration class similar to
[
PersistenceConfiguration|https://github.com/arquillian/arquillian-extensi...]
* Make
[
ConfigurationImporter|https://github.com/arquillian/arquillian-extension-...]
and
[
ConfigurationExporter|https://github.com/arquillian/arquillian-extension-...]
generic to work for currently existing configuration and newly created DBUnit specific.
* Introduce DBUnitConfiguration producer similar to
[
PersistenceConfigurationProducer|https://github.com/arquillian/arquillian...].
* Serialize new properties in
[
PersistenceExtensionArchiveAppender|https://github.com/arquillian/arquill...]
(same as for general properties)
* Introduce remote producer (which deserialize deployed property file and make it
available on the server side) similar to
[
RemotePersistenceConfigurationProducer|https://github.com/arquillian/arqu...]
* Configuration object then might be injected and used for customizing DBUnit connection
in
[
DBUnitPersistenceTestLifecycleHandler|https://github.com/arquillian/arqui...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira