activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5554) Proper support for the blueprint namespace in activemq-blueprint
Date Wed, 04 Feb 2015 15:56:34 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305346#comment-14305346
] 

Hadrian Zbarcea commented on AMQ-5554:
--------------------------------------

I think there are 2 separate issues, this is the simplest one. Steps to reproduce:

Plain vanilla Karaf (2.3.9 or 2.4.1). Install *only* the activemq-blueprint feature (otherwise
we end up in the 2nd scenario, a bit more complex). ActiveMQ 5.11.0 behaves the same way.

{code}
karaf@root> features:chooseurl activemq 5.10.1
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.10.1/xml/features
karaf@root> features:install activemq-blueprint 
karaf@root> features:list | grep activemq
[installed  ] [5.10.1          ] activemq-client               activemq-core-5.10.1    ActiveMQ
client libraries
[installed  ] [5.10.1          ] activemq                      activemq-core-5.10.1    ActiveMQ
broker libraries
[uninstalled] [5.10.1          ] activemq-broker-noweb         activemq-5.10.1         Full
ActiveMQ broker with default configuration
[uninstalled] [5.10.1          ] activemq-broker               activemq-5.10.1         Full
ActiveMQ broker with default configuration and web console
[uninstalled] [5.10.1          ] activemq-camel                activemq-5.10.1         
[uninstalled] [5.10.1          ] activemq-web-console          activemq-5.10.1         
[installed  ] [5.10.1          ] activemq-blueprint            activemq-5.10.1         
{code}
>From the console deploy the broker-blueprint.xml (attached to the deploy directory. It
will work. However, using a custom plugin (uncomment one of the two lines) gives different
errors. Arguably, using the spring namespace is not a smart idea and shouldn't even be attempted.

> 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: Jean-Baptiste Onofré
>         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)

Mime
View raw message