Ryan, I think another option would be to modify the etc/activemq-broker.xml file to publish the broker object (or the brokerfactory) in the OSGi Service Registry so you can track that again in another bundle. The file already has a sample <osgi:service /> element at the bottom for publishing the connection factory, but you could a similar thing with the broker.
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On 16 March 2010 16:45, Ryan Moquin <[email protected]> wrote: > I wanted to be able to modify connector properties on the fly. The JMX > ActiveMQ interface doesn't really do what I need. For example, if you > connect to the AMQ jms BrokerViewMBean and call addNetworkConnector(), then > it adds the network connector with a name of "localhost". Any subsequent > network connector additions throw an exception because ActiveMQ assigns all > the connectors the name "localhost" and so they conflict. There isn't an > mbean method that allows you to change the name and the property on the > networkconnector MBean itself is read only.... > > This is why I'm trying to get access to the broker directly. > > Ryan > > On Tue, Mar 16, 2010 at 11:27 AM, Tracy Snell <[email protected]> wrote: > >> On Mar 16, 2010, at 11:04 AM, Ryan Moquin wrote: >> >> > It was fairly easy to get a reference to the ActiveMQ broker in SMX3, how >> do >> > you do it in SMX4? Should it be done through JMX? Or is there a better >> > way? >> >> Why do you want it? Does JMX provide the info you need? >> >> >
