Thinking forward, it would be nice to have MutablePicoContainer.as(ComponentAdapterFactory factory, Properties....) and MutablePicoContainer.change(ComponentAdapterFactory factory, Properties...) as well. tivate with properties. Adaptive Behavior is an interesting possibility, but takes a lot of control out of the hands of the developer. Currently, you pretty much have a long chain of ComponentAdapterFactories that you activate/deac Some other mechanism to reduce the size of the CAF chains would be useful as well.