[
https://issues.apache.org/jira/browse/DELTASPIKE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974829#comment-13974829
]
Gerhard Petracek commented on DELTASPIKE-577:
---------------------------------------------
@romain:
in general i would agree with you, but imo this case is different.
#1 there are no properties for owb or weld -> it's really just about openejb.
#2 as mentioned earlier it's possible to provide the config already
#3 test-control is about the whole application and not about micro-deployments
-> you just need one config and not one per test(-class).
#4 since it's specific to openejb (for now), users who really need something
like that could still use EJBContainerRunner (org.apache.openejb:openejb-junit)
imo we should re-visit it, once we think about providing rules.
> Test-control: Add delegation of container boot
> ----------------------------------------------
>
> Key: DELTASPIKE-577
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-577
> Project: DeltaSpike
> Issue Type: Improvement
> Components: CdiControl, TestControl
> Affects Versions: 0.7
> Reporter: Karl Kildén
> Priority: Minor
>
> container.boot(); is used by Test-Control.
>
> This is nice for simple tests with cdictrl-openejb but I think it would be
> nice to have the possibility to target the boot(Map<?, ?> properties) that is
> available for the openejb container. I want Test-Control to delegate to me so
> I can boot myself.
> I am thinking something like:
> @TestControl(bootDelegate = PropertyAwareEjbBootDelegate.class)
> public interface BootDelegate {
> public void boot(CdiContainer cdiContainer);
> }
> That way tests could be way more dynamic and end users could boot the
> container in any way they want.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
