[
https://issues.apache.org/jira/browse/ARIES-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated ARIES-536:
----------------------------------
Description:
The use case is for ordering startup using start-level. If you have a bundle
that has an optional dependency on a service provided by blueprint, you have no
way to raise the chances that the service will be used from the start as
blueprint bundles are started asynchronously.
I'd like to have a way to specifiy that the blueprint bundle should be started
asynchronously, at least until a GRACE_PERIOD event would be fired, in which
case, the remaning things would be done asynchronously.
This definitely should not be used as a way to work around bad bundle behaviors
that aren't resiliant with missing dependencies, but really to ensure that when
the server boots up, services are started in an optimal order (log and
configadmin should be started before the other ones if possible).
was:
The use case is for ordering startup using start-level. If you have a bundle
that has an optional dependency on a service provided by blueprint, you have no
way to raise the chances that the service will be used from the start as
blueprint bundles are started asynchronously.
I'd like to have a way to specifiy that the blueprint bundle should be started
asynchronously, at least until a GRACE_PERIOD event would be fired, in which
case, the remaning things would be done asynchronously.
Summary: Have a way to specify a blueprint bundle should be started in
sync with the start level service as much as possible (was: Have a way to
specify a blueprint bundle should be started synchronously if possible)
> Have a way to specify a blueprint bundle should be started in sync with the
> start level service as much as possible
> -------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-536
> URL: https://issues.apache.org/jira/browse/ARIES-536
> Project: Aries
> Issue Type: New Feature
> Components: Blueprint
> Reporter: Guillaume Nodet
>
> The use case is for ordering startup using start-level. If you have a bundle
> that has an optional dependency on a service provided by blueprint, you have
> no way to raise the chances that the service will be used from the start as
> blueprint bundles are started asynchronously.
> I'd like to have a way to specifiy that the blueprint bundle should be
> started asynchronously, at least until a GRACE_PERIOD event would be fired,
> in which case, the remaning things would be done asynchronously.
> This definitely should not be used as a way to work around bad bundle
> behaviors that aren't resiliant with missing dependencies, but really to
> ensure that when the server boots up, services are started in an optimal
> order (log and configadmin should be started before the other ones if
> possible).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
