[jboss-fuse-6.1.x 121] Updating perfectus-build number to new build
[jboss-fuse-6.1.x 122] Updating perfectus-build number to new build
Make sure the download executor is correctly shutdown
Avoid waiting for the reference when calling GitDataStore#toString as it causes delays and exceptions when shutting down
Fix wrong comment in AbstractComponent
[FABRIC-609] Fix possible deadlock if datastore configuration tracker do call the Fabric api by always calling callbacks in a different thread
The DataStoreManager is over synchronized
add a connection factory service that uses config admin to configure the user name / password and broker group then discover the broker using fabric
use a perfectus.version property so we can replace that in the perfectus build to use the current perfectus build as we make it
Remove duplicate fabric-zookeeper entry from startup.properties
allow profiles which extend a broker to participate in the MQ topology view; e.g. so running jboss-fuse-full will appear in the fabric/mq/brokers tab now
ENTESB-953: fabric-agent is not installed by default in the minimal assembly
allow the ActiveMQService to be constructed from an existing connection factory
use the correct broker URL and tidied up the OSGi imports to ensure the ActiveMQConnectionFactoryService works
Update to latest hawtdispatch release.
[jboss-fuse-6.1.x 123] Updating perfectus-build number to new build
include mq-client by default in fabric builds
port the example-mq example over to use the new ActiveMQConnectionFactoryService so we've a standard way to swizzle which message group a JMS client connects to (and soon we can have mq-create generate the profile for the group...)
Fix hawtio/hawtio#642
create client connection profiles too in mq-create or via the JMX API