This applies to version 1.0.1 of the AutoConf bundle.
When a configuration is processed which contains a designate for a bundle which is not available the whole configuration is ignored and the following error is given:
"[WARN] Invalid AutoConf resource(s): "config.xml", refusing to process it..."
There are no other hints, also not when enabled verbose logging.
With version 1.0.0 of the bundle this used to work, but a warning was given:
"[WARN] Bundle "com.bdrthermea.remote.node.socket.proxy.e2e" appears not to be installed, configuration with Designate "com.bdrthermea.remote.node.socket.e2e" might not be valid!"
This previous (1.0.0) behaviour was better, but the warning is debatable as well. A configuration might be installed before a certain bundle is installed/started. Which in terms of the Configuration Admin is perfectly valid, a configuration can be available for any future bundle as well.
<Designate pid="some.installed.pid" bundle="osgi-dp:some.installed.bundle">
<Designate pid="some.not.installed.pid" bundle="osgi-dp:some.not.installed.bundle">