[ 
http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mauro Talevi updated JBEHAVE-133:
---------------------------------

          Description: 
In acceptance/integration tests is often common to have a lightweight container 
(Pico, Spring, Guice, etc ...) to configure the tests with. 

A container-supported Steps instance should be composable (either via 
constructor or setter dependency injection) with components configured in the 
container.  

Each container support will be contained in a separate optional module.

We start with Pico support, with other containers to follow. 

  was:
In acceptance/integration tests is often common to have a lightweight container 
(Pico, Spring, Guice, etc ...) to configure the tests with. 

A container-specific Steps instance would be injectable (either via constructor 
or setters) with components configured in the container.  

The LCD approach may turn out to be insufficient, so that these container 
adapters for Steps should use container-specific features.




    Affects Version/s:     (was: 2.0)
                       2.4
        Fix Version/s: 2.5
             Assignee: Mauro Talevi
              Summary: Allow Steps dependencies to be composable via 
PicoContainer  (was: Add lightweight container support for steps )

> Allow Steps dependencies to be composable via PicoContainer
> -----------------------------------------------------------
>
>                 Key: JBEHAVE-133
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-133
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.4
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 2.5
>
>
> In acceptance/integration tests is often common to have a lightweight 
> container (Pico, Spring, Guice, etc ...) to configure the tests with. 
> A container-supported Steps instance should be composable (either via 
> constructor or setter dependency injection) with components configured in the 
> container.  
> Each container support will be contained in a separate optional module.
> We start with Pico support, with other containers to follow. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to