aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Osborne (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ARIES-28) Allow extenders of blueprint to function without requiring specific declaration in deployed blueprint components xml.
Date Tue, 10 Nov 2009 13:04:27 GMT

    [ https://issues.apache.org/jira/browse/ARIES-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775395#action_12775395
] 

Andrew Osborne commented on ARIES-28:
-------------------------------------

Quiet hack a success =) I'll raise 2 new issues for the dynamic scopes & interceptors..


As the intent of this issue was to enable those 2 (excluding generic/default interceptors)
.. I think this issue should be closed out as no longer required.

> Allow extenders of blueprint to function without requiring specific declaration in deployed
blueprint components xml.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-28
>                 URL: https://issues.apache.org/jira/browse/ARIES-28
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>            Reporter: Andrew Osborne
>
> Problem:
> BeanProcessors (in conjunction with NamespaceHandlers) are useful to supplement or extend
Blueprint processing. However, unlike NamespaceHandlers, BeanProcessors must currently be
declared in the blueprint xml itself. This would mean that where Blueprint is extended through
the BeanProcessor approach, that every blueprint xml would require updating to make use of
the new function.
> Proposal:
> Like Namespace Handlers, to allow BeanProcessors to be declared in the ServiceRegistry,
as well as in the blueprint xml. 

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


Mime
View raw message