The context will manage the life cycle of the receiver.

Context now provides a method that is used to register a component
whose life cycle is to be managed by the context.  The implementation
in ContextBase simply manages a collection of LifeCycle components,
starting the component (if necessary) before it is added to the collection,
and stopping each registered component whenever the context is reset.

LOGBACK-833 Fixes for variables in sifting appender

Fix for LOGBACK-266 - FixedWindowRollingPolicy MAX_WINDOW_SIZE too small

correct ThreadPoolFactoryBean link to javadocs, correct typo in name of fieldsToCascade field in ComponentDelegate, added receiver function in ConfigurationDelegate (incomplete)

LOGBACK-833 - allow previously defined properties (in local scope) to be seen by SiftingJoranConfigurator
 * implemented part two of Ceki's suggestion
 * add getCopyOfPropertyMap() to the PropertyContainer and thus InterpretationContext
 * use local properties that are ineffect at time of creation of SiftingAppender to seed the properties map used when creting the child appenders and properties
 * removed some generics warnings
 * in AppenderFactoryBase use List.subList() rather than "copy whole array then delete and re-shuffle elements"

LOGBACK-835 - make timestamp properties default to local scope. Can be overriden by setting scope attribute

LOGBACK-266 - increase max window size of FixedWindowRollingPolicy to 20.  12 is too restrictive, and the users have voted for it to be increased

make sure that all the 'view as groovy' links work, Gaffer does not support <receiver> at this stage, nor does the translator