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

Piotr Klimczak updated ARIES-2046:
----------------------------------
    Description: 
Blueprint Spring to allow bundle blacklist to prevent unwanted namespace 
registration.

This is needed by CAMEL-16564 to allow camel-spring feature to install which is 
needed by multiple bundles, but we must not register namespace handler as the 
handler in this bundle does not support OSGi environment anymore.

I couldn't came with better approach for it.
 Analysed options like: using fragments, unregistering service, unregistering 
NS handler etc.

PR to follow

  was:
Blueprint Spring to allow bundle blacklist to prevent unwanted namespace 
registration.

This is needed by CAMEL-16564 to allow camel-spring feature to install which is 
needed by multiple bundles, but we must not register namespace handler as the 
handler in this bundle does not support OSGi environment anymore.

I couldn't came with better approach for it.
Analysed options like: using fragments, unregistering service, unregistering NS 
handler etc.


> Blueprint Spring to allow bundle blacklist to prevent unwanted namespace 
> registration
> -------------------------------------------------------------------------------------
>
>                 Key: ARIES-2046
>                 URL: https://issues.apache.org/jira/browse/ARIES-2046
>             Project: Aries
>          Issue Type: Improvement
>          Components: Blueprint
>    Affects Versions: blueprint-spring-0.6.0, blueprint-spring-1.0.0
>            Reporter: Piotr Klimczak
>            Priority: Major
>             Fix For: blueprint-spring-1.0.0
>
>
> Blueprint Spring to allow bundle blacklist to prevent unwanted namespace 
> registration.
> This is needed by CAMEL-16564 to allow camel-spring feature to install which 
> is needed by multiple bundles, but we must not register namespace handler as 
> the handler in this bundle does not support OSGi environment anymore.
> I couldn't came with better approach for it.
>  Analysed options like: using fragments, unregistering service, unregistering 
> NS handler etc.
> PR to follow



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to