Rudimentary integration with Spring containers

Nick Sieger added a comment - 09/Dec/05 8:38 PM I included a package.html file with some comments, here they are so that you don't have to download and unpack the zip to read them. Purpose To allow Picocontainers full of components to be automatically visible through adapter implementations of Spring's BeanFactory and ApplicationContext interfaces. Limitations/Compatibility Issues Spring containers reference all beans by a name (a String). Pico allows components to be stored with any object as its key (it's common to have Class objects as keys for Pico components). For now only components in a Picocontainer that have String keys will be exposed through the Spring BeanFactory. Pico doesn't have the concept of aliases, so the Spring method BeanFactory#getAliases will always return a zero-length array. Pico does not have any directly-referenceable metadata to determine if a component is a singleton. For now, the BeanFactoryAdapter#isSingleton method attempts to determine singleton status by checking if the outermost component adapter is a CachingComponentAdapter. This has obvious limitations but will work most of the time, especially considering the implementation of Pico's DefaultComponentAdapterFactory. For the Spring ListableBeanFactory#getBeansOfType(Class,boolean,boolean) method, the boolean arguments are ignored as Pico does not have sufficient metadata to fulfill the request. Several methods on PicoApplicationContextAdapter are no-ops for now as they have no meaning for a PicoContainer: publishEvent, getMessage, and getResource. (They may have some meaning in a Nano- or MicroContainer.)