Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <3364951.130291286997933404.JavaMail.jira@thor>
Date: Wed, 13 Oct 2010 15:25:33 -0400 (EDT)
From: "Joe Bohn (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Work started: (ARIES-420) Register Bean Interceptors as
 Services
In-Reply-To: <21295087.341941285163192487.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Work on ARIES-420 started by Joe Bohn.

> Register Bean Interceptors as Services 
> ---------------------------------------
>
>                 Key: ARIES-420
>                 URL: https://issues.apache.org/jira/browse/ARIES-420
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Joe Bohn
>            Assignee: Joe Bohn
>
> Our current interceptor implementation is dependent upon registering a pojo for the interceptor with the component metadata.   When constructing a bean (or service in the case of the newly introduced quiesce service interceptor) we retrieve the interceptor pojo(s) and use it in construction of the proxy.  There are potential lifecycle issues with this if the bundle which introduced the interceptor is later removed from the system.  A whiteboard pattern would improve lifecycle management such that the bundle dependencies can be better managed.

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