I have some somewhat badly-behaved code that searches through all bundles to
find resources by a particular name (META-INF/AppRegistration.xml). I've
found that this causes the framework state's timestamp to be updated, even
though there's been no configuration change. This behaviour is a bit
Hi Brian,
Is this from a cached restart? This bit of code is supposed to track both
dynamic resolution successes and failures. I would expect that on a cached
restart the dynamic resolution misses (for META-INF) would all have been
recorded and it should not cause another dynamic resolution if
