You should aim to ship with neither Spring nor PicoContainer.
It is perfectly possible to construct a set of DI components that
comprise FtpServer and in a main method do :
Foo foo = new Foo();
Bar bar = new Bar(foo);
Apple apple = new Apple();
apple.setFoo(foo);
apple.setBar(bar);
IMHO, the basic design and implementation should be XML free and
provide a
straight forward API for assembly, configuration (preferably
atomic) and the
other stuff. Any runtime platform support can be added on top of
that. Look
at Jetty for an example of this approach.
Now, Noel's suggest
On 10/2/05, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
...
> Now, Noel's suggestion for OSGi as the runtime platform is interesting, if for
> no other reason than it allows for hot deploy and reloads. But I think it
> would be possible to provide a BundleActivator and register the service(s)
> even