[
https://issues.apache.org/jira/browse/DELTASPIKE-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220778#comment-14220778
]
Gerhard Petracek commented on DELTASPIKE-785:
---------------------------------------------
@mark: i know & +1 (i just wrote the comment for the records -> thx for
providing an additional reason.)
@karl:
nonetheless it isn't portable across modules provided by deltaspike itself.
portability doesn't only mean that there is an api which can be called. the
important part is that the resulting behavior is as expected. you can use it
but only one test-container we support out-of-the-box will process it. if you
implement adapters for containers we don't support out-of-the-box, you can load
any config-file in the adapter itself.
however, we don't have to restart the discussion again. i just mentioned that
the basic topic is still the same, but it's documented and users have to take
it as it is (which means that a lot of them have to ignore it). imo that
compromise (= no api change) is ok for everybody (at least to some degree).
> Make CdiTestRunner pick up container configuration from properties file
> -----------------------------------------------------------------------
>
> Key: DELTASPIKE-785
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-785
> Project: DeltaSpike
> Issue Type: Improvement
> Components: TestControl
> Affects Versions: 1.1.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> For doing 'real' EE tests we need to be able to configure those containers
> when it boots up. CdiCtrl already has a boot(Properties) which we can use
> very easily.
> That way openejb-embedded, glassfish-embedded and wildfly-embedded can e.g.
> register DataSources for the unit tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
