-----BEGIN PGP SIGNED MESSAGE-----
Wichert Akkerman wrote:
> A common issue we are seeing is that we have eggs depending on each
> other, but they still need to load the zcml from those dependencies
> somehow. As a temporary solution to play with the concept I added
> something simple to the plone.recipe.zope2instance buildout recipe.
> It allows you to define entrypoints like this:
> "zope.zcml" : [
> "meta = plone.session",
> "configure = plone.session",
> this tells the system to load meta.zcml and configure.zcml from plone.session.
> I am not quite sure what the best way to hook this into Zope itself is.
> For Zope 2 we can do it in Five, since that is where all the zcml loading
> logic currently is. Or we could move that into Zope2 itself somewhere.
> I'm not familiar enough with Zope3 to know what the best place would be there.
> One problem is ordering: the zope.component zcml needs to be loaded first.
That's a packaging bug: any package whose ZCML won't load without
having zope.component loaded already needs to add the explicit inclusion
(duplicates do *not* conflict for the <include> directive).
> Perhaps we need to build an egg dependency graph and walk through that
> to load zcml entry points in the right order. As long as all dependencies
> are registered correctly that should work.
I'd rather fix the ZCML files.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -