[arquillian-issues] [JBoss JIRA] (ARQ-754) Change the way how Drone context is intialized

[Karel Piwko (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679754#comment-12679754 ] 

Karel Piwko commented on ARQ-754:
---------------------------------

Drone currently requires to go through following events:

For field injection

1/ BeforeSuite -> read the class and configure all @Drones
2/ DroneConfigured -> Instantiate all @Drones
3/ TestEnricher -> Inject all @Drones
4/ AfterSuite -> destroy all @Drones

For method parameter injection:

1/ Before -> Configure all @Drones
2/ MethodDroneConfigured -> Instantiate all Drones
3/ TestEnricher -> Inject all @Drones
4/ After -> Destroy all @Drones

This effectively means that for a TestEnricher to have access to @Drones from JBehave runner,

we need to change location where instances are injected and where they are disposed. We can't directly create instances in TestEnricher lazily, because there would be now way how to properly dispose them.

I'm convinced that a proper way how this should be solved is to provide @Drone events as a part of Drone SPI, so jbehave can fire these events itself.

However, this change cannot be introduced in CR3, therefore is will be scheduled for 1.1.0 stream.


                
> Change the way how Drone context is intialized
> ----------------------------------------------
>
>                 Key: ARQ-754
>                 URL: https://issues.jboss.org/browse/ARQ-754
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Drone
>    Affects Versions: drone_1.0.0.CR3
>            Reporter: Karel Piwko
>            Assignee: Karel Piwko
>             Fix For: drone_1.1.0.next
>
>
> Introduce either a lazy loading or storing some lightweight object in the Arquillian session to allow jbehave extension to inject Drone instances.

--
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