You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2015/03/10 00:23:38 UTC

[jira] [Resolved] (AMQ-5554) Proper support for the blueprint namespace in activemq-blueprint

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

Hadrian Zbarcea resolved AMQ-5554.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 5.11.2
                   5.10.3

This is fixed and released by [~dkulp] in ARIES-1293. 

The release version indicate 5.10.3 and 5.11.2, however no changes are required in ActiveMQ and it will work with earlier versions (it's just that these two releases come after the aries blueprint.cm 1.0.6 which provides the fix).

In this particular case, to use <bean> custom plugins in the activemq configuration one must use a blueprint-cm version 1.0.6 or newer and use bean from the blueprint-ext/v1.5.0 namespace, or newer:
{code}
<ext:bean xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.5.0" ... />
{code}

> Proper support for the blueprint namespace in activemq-blueprint
> ----------------------------------------------------------------
>
>                 Key: AMQ-5554
>                 URL: https://issues.apache.org/jira/browse/AMQ-5554
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: OSGi/Karaf
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Daniel Kulp
>             Fix For: 5.10.3, 5.11.2
>
>         Attachments: broker-blueprint.xml
>
>
> It would be great to support blueprint <bean/> directly in broker <plugins/> when using activemq-blueprint.
> It will allow users to do configuration like:
> {code}
> <plugins>
> <bean class="my.plugin" xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"/>
> </plugins>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)