activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Resolved: (AMQ-853) Make BrokerFactoryBean use pre-existing app context as parent
Date Tue, 01 Aug 2006 11:39:24 GMT
     [ ]

james strachan resolved AMQ-853.

    Resolution: Fixed

Patch applied with thanks. With more complex patches its better to actually supply a patch
file - see the [creating patches|].
This patch was so simple I think I've not messed it up :)

> Make BrokerFactoryBean use pre-existing app context as parent
> -------------------------------------------------------------
>                 Key: AMQ-853
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 4.1
>            Reporter: Jason Carreira
>             Fix For: 4.1
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
> I've made a local enhancement to the BrokerFactoryBean to make it where your activeMQ
XML configuration files refer to beans configured in your Spring application context. Basically
I just made the BrokerFactoryBean implement ApplicationContextAware so the ApplicationContext
will be set, then in afterPropertiesSet() when it's creating the context for the config resource
location, it does this:
> context = new ResourceXmlApplicationContext(config, applicationContext)
> passing in the Spring application context as the parent application context for the ResourceXmlApplicationContext.
> I did this for myself so I could use the same DataSource as the backing DataSource for
JDBC persistence. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message