You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/07/11 11:44:00 UTC

[jira] [Updated] (KARAF-531) Provide a KarafContainer similar to what we have with CamelContainer to start a karaf instance within a project and register components

     [ https://issues.apache.org/jira/browse/KARAF-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-531:
---------------------------------------

      Component/s: runtime
    Fix Version/s: 3.1.0

> Provide a KarafContainer similar to what we have with CamelContainer to start a karaf instance within a project and register components
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-531
>                 URL: https://issues.apache.org/jira/browse/KARAF-531
>             Project: Karaf
>          Issue Type: New Feature
>          Components: runtime
>            Reporter: Charles Moulliard
>             Fix For: 3.1.0
>
>
> Containers exist for a lot of different standards like EJB, JPA, Camel, Spring, Web and allow to provide a scope and a boundary for the project itself. Karaf does not provide this feature and in consequence reduce the possibilities in an integration test to test our bundles on Karaf. This is why I suggest that we create this container for testing purpose (at beginning) and could be extended to setup/configure the platform. This container will allow to proxy pax-exam(2) and facilitate the configuration of our tests using also karaf tooling helper class. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira