Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <441020212.497401267029876656.JavaMail.jira@brutus.apache.org>
Date: Wed, 24 Feb 2010 16:44:36 +0000 (UTC)
From: "Jeremy Hughes (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Updated: (ARIES-63) Add getters to
 ComponentDefinitionRegistry for Blueprint Container, Blueprint Bundle,
 Blueprint Bundle Context and Blueprint Converter
In-Reply-To: <1897756608.1259771300624.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-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hughes updated ARIES-63:
-------------------------------

    Fix Version/s: 0.1

> Add getters to ComponentDefinitionRegistry for Blueprint Container, Blueprint Bundle, Blueprint Bundle Context and Blueprint Converter
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-63
>                 URL: https://issues.apache.org/jira/browse/ARIES-63
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>            Reporter: Andrew Osborne
>            Assignee: Valentin Mahrwald
>            Priority: Minor
>             Fix For: 0.1
>
>
> The 4 listed objects are defined by the spec to be available, via specified id's for injection. 
> They are generally useful objects for a variety of purposes, but currently there is no way for a NamespaceHandler to obtain these, unless it happens to be aware both that they are present under those id's within the component definition registry, AND how to dereference them through the PassThrough approach. Understanding both of these creates rather a strong link between any NamespaceHandler, and our current internals.
> As such, the proposal is to add getters to the ComponentDefinitionRegistry, that do the dereferencing through the passthroughmetadata's internally, keeping that implementation choice isolated from any NamespaceHandler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.