That's kinda what I would have in mind. So the rest is a matter of naming.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.
What about layering this like
CocoonBean (non-Avalon) -> Berin's "clean access interface" -> Cocoon
I did not yet look at the code - does this make sense?
Regards, Upayavira
