[
https://issues.apache.org/jira/browse/HIVEMIND-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569291#action_12569291
]
Johan Lindquist commented on HIVEMIND-117:
------------------------------------------
As part of looking at HIVEMIND-116, this fits into the same pattern and could
be bundled as part of that. Does that make sense or am I missing something
essential?
> add an activate-method and passivate-method attribute to the construct
> element of BuilderFactory
> ------------------------------------------------------------------------------------------------
>
> Key: HIVEMIND-117
> URL: https://issues.apache.org/jira/browse/HIVEMIND-117
> Project: HiveMind
> Issue Type: New Feature
> Components: framework
> Affects Versions: 1.1
> Reporter: Richard Hensley
>
> Add attributes to the construct element of BuilderFactory that supports the
> life cycle management of Pooled services. These attributes could be used in
> place of the PoolManageable interface. The motiviation for this feature is to
> make the services container agnostic. The beans we construct need to operate
> in a Spring environment and a Hivemind environment depending on the
> deployment choices.
> Here is a start at a specification.
> add a activate-method attribute to the construct element recognized by
> BuilderFactory
> When the activate-method is specified, the method must be a public void
> method taking no parameters. This method is called either just before the
> service is created, or just after the service is removed from the service
> pool and bound to a new thread. When autowire-service is enabled and
> activate-method is not specified, BuilderFactory will introspect for a method
> called activateService() and treat it as a activate-method. If the service
> also implements the PoolManageable interface, the activate-method is called
> before the PoolManageable.activateService() method.
> add a passivate-method attribute to the construct element recognized by
> BuilderFactory
> When the passivate-method is specified, the method must be a public void
> method taking no parameters. This method is called when a service is unbound
> from a thread, just before being returned to the service pool. When
> autowire-service is enabled and passivate-method is not specified,
> BuilderFactory will introspect for a method called passivateService() and
> treat it as a passivate-method. If the service also implements the
> PoolManageable interface, the passivate-method is called before the
> PoolManageable.passivateService() method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
