|
| |
| 1. PicoContainer | | By: | | | License: | Open Source | | URL: | http://www.picocontainer.org/ | | Description: | PicoContainer is a lightweight and highly embeddable container for components that honour Dependency Injection.
|
| 2. NanoContainer | | By: | | | License: | Open Source | | URL: | http://www.nanocontainer.org/ | | Description: | The scope of the NanoContainer project is to complement the PicoContainer project, providing it with additional functionality. The project comprises of several components which can either be adaptions in various guises of PicoContainer (eg composition by-class-name rather than by-class), or adaptations to external components bringing them closer to the Dependency Injection ideal - particularly Constructor Injection
|
| 3. Carbon | | By: | | | License: | Mozilla Public License | | URL: | http://carbon.sourceforge.net/ | | Description: | Carbon is a light-weight component model and services framework providing enterprise quality services. Carbon is built on the following principles:
* Create a more flexible architecture via a decoupled, metadata-centric system
* Reduce complexity by providing access to services as small replaceable components
* Encourage the separation of concerns, resulting in code assets that are easier to maintain, adapt and reuse in a complex and dynamic operating environment
* Improve quality with highly documented, fully tested code
|
| 4. Excalibur | | By: | | | License: | Apache Software License | | URL: | http://excalibur.apache.org/index.html | | Description: | Excalibur is an open source software project of The Apache Software Foundation. Our primary product is a lightweight, embeddable Inversion of Control container named Fortress that is written in java.
|
| 5. gravity | | By: | | | License: | Apache Software License | | URL: | http://gravity.dev.java.net | | Description: | This is a dependency and configuration management framework that allows multiple forms of configuration via a plugin model with a primary focus on the Dependency Injection / Inversion of Control (IoC) design pattern. The framework comes with a default BeanShell plugin for configuring the components.
|
| 6. Soto | | By: | | | License: | Apache Software License | | URL: | http://www.sapia-oss.org/projects/soto | | Description: | Soto stands for "service oriented technology"; it will offer various tools/frameworks intented to provide building blocks for service-oriented architectures. Soto's core is a lightweigth container framework allowing to "wire" services through a convenient XML format. Soto in addition supports a "layered" logic approach: different "logic domains" (known as "layers") can be mapped on top of service instances, sparing the developer from aggregating various types of logic into unmanageable blobs - this is similar to what AOP attempts to solve, but at a higher-level: the "layer" concept needs not being implemented with byte code manipulation, advices, pointcuts, and the likes.
|
| 7. JICE | | By: | | | License: | GNU Library or Lesser General Public License (LGPL) | | URL: | http://jicengine.sourceforge.net | | Description: | JICE is an XML-based Inversion of Control (IoC) Container - a tool for constructing and configuring application objects. JICE consists of:
* JIC Language - an XML format for describing the objects in a Java application.
* JIC Engine - A Java application that constructs graphs of Java objects based on the instructions the XML files.
|
| 8. HiveMind | | By: | | | License: | Apache Software License | | URL: | http://jakarta.apache.org/hivemind/ | | Description: | HiveMind is a services and configuration microkernel:
* Services: HiveMind services are POJOs (Plain Old Java Objects) that can be easily accessed and combined. Each service ideally defines a Java interface it implements (but this is no longer mandatory). HiveMind takes care of instantiating and configuring each service just as necessary. HiveMind lets services collaborate with each other via dependency injection.
* Configuration: HiveMind allows you to provide complex configuration data to your services in a format you define. HiveMind will integrate the contributions of such data from multiple modules and convert it all into data objects for you. HiveMind configurations allow for powerful, data-driven solutions which combine seemlessly with the service architecture.
* Microkernel: HiveMind is a framework for creating applications, not an application, or even an application server, itself. The 'core' of HiveMind is the startup logic that knows how to parse and understand the module deployment descriptors, and use that information to instantiate and initialize all those services and configurations.
|
| 9. DNA | | By: | | | License: | Open Source | | URL: | http://dna.codehaus.org/ | | Description: | DNA is a lightweight Inversion of Control (IOC) framework.
|
| 10. Loom | | By: | | | License: | Open Source | | URL: | http://loom.codehaus.org/ | | Description: | Loom is a micro-kernel designed and implemented on top of the DNA framework. It supports components developed using the Avalon framework. In the future Loom will also support DNA and Pico components.
Loom provides a number of facilities to manage the environment of server applications. Such facilities include log management, classloading, thread management and security. Future releases will conditionally support extra facilities such as central server management, server pools, and other tools aimed at reducing the time to market.
The API defines a standard method of piecing together server components and creating a server.
|
| 11. Yan | | By: | | | License: | Open Source | | URL: | http://yan.codehaus.org/ | | Description: | Yan container stands for Yet Another Non-intrusive container for object dependency injection.
The core of Yan is a compact Java API with no dependency to any other lib.
Around the tiny core, are services such as component monitoring, life cycle management, xml configuration etc.
|
| 12. Spice | | By: | | | License: | Open source | | URL: | http://spice.codehaus.org/ | | Description: | Spice is a repository of Components which support Component Oriented Programming (COP) paradigms - in particular, the Inversion of Control (IoC) design pattern.
|
|