plone.behavior 1.0.2

Infrastructure for maintaining a registry of available behaviors

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!

What's new in plone.behavior 1.0.2:

  • Remove dependence of tests on [davisagli]
Read full changelog
send us
an update
BSD License 
Martin Aspeli
ROOT \ Internet \ Plone Extensions
plone.behavior is a Plone product that provides optional support for "behaviors". A behavior is a re-usable aspect of an object that can be enabled or disabled without changing the component registry.

A behavior is described by an interface, and has metadata such as a title and a description. The dotted name of the interface is the unique name for the behavior, from which the metadata can be looked up. When the behavior is enabled for an object, you will be able to adapt the object to the interface. In some cases, the interface can be used as a marker interface as well.

As an example, let's say that your application needs to support object-level locking, and that this can be modeled via an adapter, but you want to leave it until runtime to determine whether locking is enabled for a particular object. You could then register locking as a behavior.


This package comes with support for registering behaviors and factories. It does not, however, implement the policy for determining what behaviors are enabled on a particular object at a particular time. That decision is deferred to an IBehaviorAssignable adapter, which you must implement.

This package also does not directly support the adding of marker interfaces to instances. To do that, you can either use an event handler to mark an object when it is created, or a dynamic __providedBy__ descriptor that does the lookup on the fly (but you probably want some caching).

The intention is that behavior assignment is generic across an application, used for multiple, optional behaviors. It probably doesn't make much sense to use plone.behavior for a single type of object. The means to keep track of which behaviors are enabled for what types of objects will be application specific.


A behavior is written much like an adapter, except that you don't specify the type of context being adapted directly. For example:

from zope.interface import Interface, implements

class ILockingSupport(Interface):
 """Support locking

 def lock():
 """Lock an object

 def unlock():
 """Unlock an object

class LockingSupport(object):

 def __init__(self, context):
 self.context = context

 def lock(self):
 # do something

 def unlock(self):
 # do something

This interface (which describes the type of behavior) and class (which describes the implementation of the behavior) then need to be registered.

The simplest way to do that is to load the meta.zcml file from this package and use ZCML:

< configure
 i18n_domain="my.package" >

 < include package="plone.behavior" file="meta.zcml" / >

 < plone:behavior
 title="Locking support"
 description="Optional object-level locking"
 / >

< /configure >

After this is done - and presuming an appropriate IBehaviorAssignable adapter exists for the context - you can adapt a context to ILockingSupport as normal:

locking = ILockingSupport(context, None)

if locking is not None:

You'll get an instance of LockingSupport if context can be adapted to IBehaviorAssignable (which, recall, is application specific), and if the implementation of IBehaviorAssignable says that this context supports this particular behavior.

It is also possible to let the provided interface act as a marker interface that is to be provided directly by the instance. To achieve this, omit the 'factory' argument. This is useful if you need to register other adapters (including views and viewlets) for instances providing a particular behavior.

Like the IBehaviorAssignable plumbing, marker interface support needs to be enabled on a per-application basis. It can be done with a custom __providedBy__ decorator or an IObjectCreatedEvent handler for applying the marker. A sample event handler is provided with this package, but is not registered by default

Please see behavior.txt, directives.txt and annotation.txt for more details.

Last updated on May 23rd, 2011


#behaviors support #Plone extension #Plone #behaviors #registry #behavior

Add your review!