activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject amq 5.4 and osgi/blueprint
Date Fri, 05 Feb 2010 20:01:07 GMT
For the geronimo 3 amq integration I've been working on getting amq  
5.4 to run in de-springified osgi/buleprint using the xbean-blueprint  
NamespaceHandler I ported.  I think I have at least a basic broker  
starting up.

I'd like to make a few changes so this will work better:

1. Several classes use what I think are obsolete spring-isms namely  
implementing the spring interfaces InitializingBean, DisposableBean,  
and FactoryBean to tell spring stuff.  IIUC a more up-to-date  
technique is to set this in the xml or, using xbean, using InitMethod  
and destroyMethod annotations.  For the classes that are otherwise not  
spring-dependent I'd like to switch to the xbean annotations.  The  
classes involved are:

activemq-core/src/main/java/org/apache/activemq/spring/ (has other spring-isms)

In addition, I need to expose
to xbean.

2. To allow other bundles to interact with amq in osgi, it looks like  
org.apache.activemq.util.osgi.Activator needs to be run.  One  
possibility would be to just install it as the bundle activator for  
activemq-core, this is what I've tried and appears to work OK.  If  
this doesn't seem like a good idea to everyone I think I can just  
install it as a blueprint bean in a geronimo bundle.


david jencks

View raw message