"Bruno Dumon" <[EMAIL PROTECTED]> wrote: > > Haven't thought deeply about this, but just some thoughts (without > choosing either way for now): > > - for Cocoon-specific components (e.g. sitemap components) it doesn't > matter that much, except for the porting effort, both for us and for > users who have custom-developed components. Yepp.
> > - for more generic components, one could argue that it should be easy > enough to write a wrapper component around it that implements the > correct interfaces. This for both directions, i.e. embedding non-Cocoon > components in Cocoon or embedding Cocoon-components in other locations. Yes, but if there are classloading problems when the avalon interfaces are used directly, than you have these problems with the wrappers as well. Carsten
