It seems pretty obvious though, that there are two contrasting issues here:
1. Cocoon's charter is not to be a container. Having an internal container
implementation violates this idea.
There is no intention whatsoever to make the container a separately distributable artefact of the project. It just sits at the core of Cocoon.
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source Java & XML An Orixo Member Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
