Hi,

with the recent release of Karaf 2.3.2 I updated my integration tests to
use the lastes Karaf version. Test framework is Pax-Exam 3.1.0 with
Container Karaf-Pax-Exam. Unfortunately something has changed with the
timing of the test start as now I get ClassNotFound for injected interfaces
even though they are available if I retrieve them inside the test via
service-lookup.

I also included the command shell in the test via commandprocessor and can
see that declared bundles are either missing or not in active state yet. If
I however put a Thread.sleep() into the test method without injecting
references I can see that all configured bundles are deployed and active
calling "osgi:list".

Is there a workaround to tell Pax-Exam to wait longer before starting the
test? What is the trigger for Pax-Exam to start and do you have an idea why
it is behaving differently in Karaf 2.3.2 compared to 2.3.1 ?

Thanks and Regards,
Michael

Reply via email to