Hi Harald, I tried the "timeout" option on the filter but it did not have to seem any impact on initial testing. Seems the probe gets initialized prematurely anyway.
I will raise an issue and will provide a test for this. Kind Regards, Michael 2013/7/12 Harald Wellmann <[email protected]> > Hi Michael, > > as a workaround, you can try adding > > @Filter(timeout = 30000) > > to your injection points (timeout in ms, choose any appropriate value). > > But I suppose the real cause is that the probe bundle is started > before all Karaf bundles are active. Pax Exam's "pure" OSGi containers > were changed a while ago to check the status of all provisioned > bundles before starting the test probe, and I suspect an equivalent > check does not yet exist in the Karaf container. > > Would be helpful if you could provide a minimal test case for this > scenario and open a JIRA issue. > > Best regards, > Harald > > > > 2013/7/12 Michael Täschner <[email protected]>: > > 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 > > > > -- > > -- > > ------------------ > > OPS4J - http://www.ops4j.org - [email protected] > > > > --- > > You received this message because you are subscribed to the Google Groups > > "OPS4J" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > >
