[arquillian-issues] [JBoss JIRA] (ARQ-1778) Add global container setting for bundle autostart after deployment.
Martin Basovnik (JIRA)
issues at jboss.org
Sat May 17 11:07:56 EDT 2014
[ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968568#comment-12968568 ]
Martin Basovnik commented on ARQ-1778:
--------------------------------------
I would like to create a unit test for this feature but I do not want to modify {{arquillian.xml}} file. I have created *ResourceProvider* for container configuration class but injection into my test works only in client tests ({{@RunAsClient}}). When I modify the configuration and then execute another "in-container" test, some classes are missing in deployed bundle (e.g. {{KarafManagedContainerConfiguration}} and others). Why? I do not use this class in this method, just in client method.
> Add global container setting for bundle autostart after deployment.
> -------------------------------------------------------------------
>
> Key: ARQ-1778
> URL: https://issues.jboss.org/browse/ARQ-1778
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: OSGi Containers
> Reporter: Martin Basovnik
> Assignee: Thomas Diesler
>
> Bundle is not started automaticly after deployment. It is possible to use annotation {{@StartLevelAware(autostart = true)}} for specific test now.
> Add new global container property *autostartBundle*. This will cause autostart of every deployed bundle via container's public method {{deploy(Archive<?> archive)}}. If either annotation of specific bundle or container property will have positive value bundle will be started. One setting with positive value will always override the second one with negative value.
> Property type will be {{boolean}} and default value {{false}}.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the arquillian-issues
mailing list