Problem with ConfigurationAdminAssert

[Cristiano Gavião]

Hello,

While testing a Factory PID I found a possible bug in the method below or with pax-exam4.1. at least when running debug with pax-exam and Equinox-Luna (where I could debug) I'm getting a different behaviour than expected.

 

public static void assertConfigurationAvailable(String message, BundleContext bc, String pid, String factoryPid) {
        assertConfigurationAvailable(message, bc, createConfigurationFilter(pid, factoryPid, bc.getBundle().getLocation()));
    }

I need to ensure that a factory configuration was added and later to ensure that one service was created for this configuration (DS with Required configuration policy).

I'm using the method this way : ConfigurationAdminAssert.assertConfigurationAvailable(bc, null,"servicefactory1");
It fails and what I saw while debugging is that the filter created by the method is this:

(&(service.factoryPid=servicefactory1)(service.bundleLocation=local))

if I remove (service.bundleLocation=local)  from filter, the factory configuration is found and test pass...

any one have tried this with pax-exam ?

[Dmytro Pishchukhin]

Hi Cristiano,

can you reproduce the problem with another pax-exam or equinox version?