The purpose of the CocoonBean

[Upayavira]

I note from commit messages that Berin has completely changed the 
purpose of the CocoonBean. The CocoonBean is a published (if not 
entirely stable) interface, and therefore I think this needs some 
discussion before it can be changed significantly.

It seems to me that Berin is trying to create a bean to have a clean 
access to the Cocoon class, which seems fair enough - I've got no 
objection to that.

However, it is a completely different thing to the current bean, which 
is much more geared around offering a non-Avalon interface to Cocoon for 
inclusion in other java code.

I think that the CocoonBean should be left in its place, and that 
Berin's bean should be placed somewhere else (and named suitably so as 
not to cause user confusion when people go hunting for the CocoonBean).

What do others think?

Regards, Upayavira