For concise article about how Pax Exam thinks, read [1]. More specifically, its concept 6 and 7:
*Key Concept 6: Test Methods are exposed as OSGi Services: *Using an Extender Pattern we make the test methods "callable" via the OSGi Registry. In Pax Exam 1.x tests must have a default constructor. (..). *Key Concept 7: Bundle Context Injection: *There is only one way to communicate with the environment for the test probe code (code inside @Test methods). This is the Bundle Context that you may obtain either via field injection (just have a field in your Testcase of type BundleContext) or Parameter injection (have a parameter of type BundleContext). It was an early decision not to directly re-implement a full blown Dependency Injection Framework. Using Bundle Contexts you always can put another, more user friendly, layer on top. [1] http://okidokiteam.com/blog/2011/1/18/understanding-pax-exam-1x-part-i.html Nothing more, nothing less. HTH, Toni On Tue, Jan 25, 2011 at 6:55 PM, Luca Stancapiano < [email protected]> wrote: > Hi all.... > Reading the documentation seems that I need to configure manually the > services of a bundle that I would test. Can I simply put the bundle > information in PAX so it execute the whole deploy inside felix (included > services and components)? > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > -- *Toni Menzel - http://www.okidokiteam.com*
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
