Ralph Goers wrote:
Carsten Ziegeler wrote:
b) Plugins or portlets I could imagine to bundle portles for the cocoon portal engine as simple blocks conforming to a cocoon portlet contract. So the portal block uses the portlet blocks, but in addition a portlet block needs access to some portal services. The same would apply if you would use the block concept to implement some kind of plugins.
I don't see this as a circular dependency. While portlets are certainly dependant on the portal block, the converse is not true. The portal has a dependency on the interface that portlets implement, not the actual portlets themselves. Presumably, they are simply "looked up". Anything else would be like saying Avalon is dependent on Cocoon, which certainly is not true.
Ah, ok, I see your point - yes, you're right. But somehow you have to tell the portal how to get the portlets. Perhaps this is a different issue. Hmm..
It should be composition: an application is composed of portal block and several portlet blocks. Application then will know its portlets, and it can feed this knowledge into the portal, one way or another...
Vadim
