[arquillian-issues] [JBoss JIRA] (ARQ-1778) Add support for automatic starting of bundle after installation

[Martin Basovnik (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Basovnik updated ARQ-1778:
---------------------------------

    Description: 
Bundle is not started automaticly after installation now.

Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. 

BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers.

Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem.

  was:
Bundle is not started automaticly after installation now.

Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. 

BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers.



> Add support for automatic starting of bundle after installation
> ---------------------------------------------------------------
>
>                 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 installation now.
> Create new container property **autostartBundle**. It's type will be {{boolean}} and default value {{false}}. 
> BundleContext cannot be injected in application servers (e.g. EAP) and arquillian tests cannot be shared now with both containers.
> Annotation {{@org.jboss.arquillian.osgi.StartLevelAware(autostart = true)}} does not solve this problem, because maven artifact with this annotation can add another container on classpath and this is problem.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)