Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <1697997095.203911265881353433.JavaMail.jira@brutus.apache.org>
Date: Thu, 11 Feb 2010 09:42:33 +0000 (UTC)
From: "Valentin Mahrwald (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Closed: (ARIES-59) Optional service reference cause
 blueprint to wait
In-Reply-To: <2000761906.1259663120651.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ARIES-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Mahrwald closed ARIES-59.
----------------------------------


> 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.