Thanks Bertrand.
You're right that currently, in Bricks, the HiveMind component manager is completely separate from Cocoon's, this deserves to be improved.
I recall a bit of your CocoonGT 2005 talk where you mentioned that.
...what I'd do is to build the HiveMind Registry in a different way: creating the Registry in a Cocoon component which implements ThreadSafe and Contextualizable would allow you to inject the Cocoon Context (and other components if needed) into the Registry when it's initialized. And you can still add the Registry as a context attribute to be backwards-compatible with the current Bricks code.
A similar thought had occurred to me... I'll look into it.
I'd be happy to integrate any improvements in bricks-cms about this, in order to build a better bridge between the HiveMind and Cocoon "worlds".
Is Hivemind still worth using as a 'best of practice' component manager? I've never used it but is Spring the current pretender to the throne of preferred Cocoon component manager?
David Legg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
