Ales Justin [http://community.jboss.org/people/alesj] created the discussion "GC shutdown and wiring" To view the discussion, visit: http://community.jboss.org/message/547120#547120 -------------------------------------------------------------- As per this OSGi-dev discussion: * http://www.mail-archive.com/osgi-dev@mail.osgi.org/msg01406.html http://www.mail-archive.com/osgi-dev@mail.osgi.org/msg01406.html mailto://www.mail-archive.com/osgi-dev@mail.osgi.org //www.mail-archive.com/osgi-dev(a)mail.osgi.org/msg01406.html we're missing "GC" notion on available capabilities / deployments. We should be still able to wire to undeployed "GC" based deployments, but we're definitely cleaning up too much. This can be seen in Deployers test - MockClassLoaderDependenciesUnitTestCase::testWildcardWithGC() where you comment out first B.class loading attempt - assertLoadClass(clA, B.class, clB). The extra delegates never get created, and we cannot resolve them later in WildcardDelegateLoader. Perhaps this is actually OK for wildcards, since it means no-one actually tried to load anything with the requested package? But this would definitely not be OK for non-dynamic wiring, as any later deployment wouldn't be able to wire up to "GC-ed" deployment. How to "enable" this GC notion into deployments as well? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/547120#547120] Start a new discussion in JBoss Microcontainer Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]