Ugo Cei wrote:
I understand. I wasn't so much suggesting looking at the code but the design principles. The only way heterogeneous component types would work in a Cocoon environment is employing something like what I suggested. Granted there may be other ways, but IMO that is the most easily sustainable way.
Can you explain what you mean by "heterogeneous components"?
heterogeneous simply means "of different types". I.e. the ability to mix Spring style components with Avalon style components and pico style components.
You do have to draw boundaries of where and how these components are defined so that you can know how to instantiate them.
