[jira] Resolved: (AMQ-673) A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker.

["Hiram Chirino (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-673?page=all ]
     
Hiram Chirino resolved AMQ-673:
-------------------------------

    Resolution: Fixed

If you now use:

    <bean id="broker1" class="org.apache.activemq.xbean.PooledBrokerFactoryBean">
      <property name="config" value="classpath:activemq.xml"/>
    </bean>

    <bean id="broker2" class="org.apache.activemq.xbean.PooledBrokerFactoryBean">
      <property name="config" value="classpath:activemq.xml"/>
    </bean>


broker1 and broker2 will be the same bean instance.  if the config value was different, then you would have a different bean instance.  Pooling is keyed of the config value.



> A way to Pool embedded brokers so that if multiple spring contexts are being used which define an embedded broker, only the first one starts up the broker.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: AMQ-673
>          URL: https://issues.apache.org/activemq/browse/AMQ-673
>      Project: ActiveMQ
>         Type: New Feature

>   Components: Broker
>     Reporter: Hiram Chirino
>     Assignee: Hiram Chirino
>      Fix For: 4.0 RC 2

>
>
> A good use case would be where you want to use a single embedded broker across multiple webapps.  Only the first web app should start the embedded broker.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira