On Mar 7, 9:01 am, Wichert Akkerman <[EMAIL PROTECTED]> wrote:
> <hannosch> it uses an internal API which we didn't wrap
> <hannosch> but that's standard baseglobalcomponents behaviour and
>            would happen with listen as well for example
> <hannosch> it uses registry.utilities.lookup() instead of any
>            registry.getUtility or registry.queryUtility methods

Ah I see.  The problem is that outside code is directly accessing the
utility registry directly (as a sub item of the actual component
registry).  Since a lot of code probably already does this it probably
makes most sense to simply override the lookup call on the utility
registry itself.  I've  gone ahead and cut a branch to do this (so I
don't mess up trunk in the meantime for CMF testing) but it's not
ready yet.  You can see this in my rocky-override-utility-registry
branch at:
http://svn.zope.org/five.localsitemanager/branches/rocky-override-utility-registry/src/five/localsitemanager/registry.py?rev=73030&view=log

The problem I've run into so far though is that due to the utility
registry not being aq-aware it's difficult to get to the site from
within the utility registry.  I attempted to make things aq aware but
things quickly blew up.  Anyhow, I'll try to look at this again
soonish but not anymore today.  If anyone has any suggestions in the
meantime, I'm all ears.

Regards,
Rocky

_______________________________________________
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to