AccessControl redefines zcml class directive without factory subdirective

Bug #870921 reported by Patrick Gerken
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Medium
Unassigned

Bug Description

Both AccessControl and zope.security declare the zcml directive class.
AccessControl first loads zope.security.
Both do not define a discriminator, because of that, there will be no ConfigurationConflict.
Because AccessControl depends on zope.security, it will always overwrite the configuration of zope.security.
AccessControl does NOT declare the subdirective factory.
If one uses the subdirective factory, like zope.site does, zope does not know how to handle it, because it only uses the subdirectives declared in AccessControl.

I think this is an error in AccessControl, but since this configuration looks like copied from zope.security, just without that specific subdirective, I assume there must be a reason for it and the real culprit is somewhere else.

Changed in zope2:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.