You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2009/12/01 11:37:22 UTC
[jira] Commented: (ARIES-59) Optional service reference cause
blueprint to wait
[ https://issues.apache.org/jira/browse/ARIES-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784160#action_12784160 ]
Valentin Mahrwald commented on ARIES-59:
----------------------------------------
See also ARIES-60 for the issue of blocking the blueprint extender itself.
> Optional service reference cause blueprint to wait
> --------------------------------------------------
>
> Key: ARIES-59
> URL: https://issues.apache.org/jira/browse/ARIES-59
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Valentin Mahrwald
> Assignee: Valentin Mahrwald
>
> Section 121.7.9 suggests with its definition of "optional" ...
> "optional - Optional indicates that the satisfaction of this reference is not relevant for any registered services, or for the grace period."
> that optional service references should not cause a wait when the application tries to use the service. However, in the current implementation the blueprint container will block on optional service references as well as mandatory ones.
> This is quite a major problem since it means the blueprint extender itself can get blocked up if enough (3) bean init methods try to use optional and not-satisfied service references.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.