Relative Volunteering

Authors: Paul Hammant

Overview

OK, so you think you might want to volunteer for something, but not PicoContainer itself ?

Context: The container landscape for Pico and Nano are fairly crowded with developers. We have some big hitters steering our development too. The .NET port is already underway. It should be shadowing the development for the Java version. Clearly, there are features of the Java version that do not have peer equivalence in the .NET version. There are also features that are just not needed.

So how about volunteering for something that is related to PicoContainer?

Components.

What we really need are components. Lots of them. In most case it will be adaptations of existing beans. We're not interested in in having components in the PicoContainer or NanoContainer projects. We are interested in the having synergies with related projects. If someone wants to make a component to the Pico design then we'll support it.

One we consider really important is some subtle componentization of the excellent Jetty server. As well as lacing together the components of Jetty via Pico, it would be nice to have servlets that were Pico components (breaking the Servlet spec slightly). Thus an extended Jetty could instantiate servlets that had dependencies specified in their constructors.

Watch this space for a component (ComponentHaus) registry site being set-up