#140 refactor to reuse code from fabric-agent across fabric-openshift and process-fabric
Epic commit: have the fabric-create command wait for the ZK profile to be successfully deployed.
first spike of a camel component to connect to the fabric A-MQ cluster using broker groups from mq-create's profiles
[jboss-fuse-6.1.x 127] Updating perfectus-build number to new build
whoops removed cruft
fixed up the mq-camel component to use the correct camel component resolver property ("component") and added a feature
renamed bundles to make them more obvious; mq-fabric-client -> mq-fabric-cf to nightlight its a connection factory for mq and fabric (i.e. fabric based broker groups) and mq-camel -> mq-fabric-camel to highlight its for connecting to fabric based broker groups; using the mq-create managed client profiles)
refactored the embedded camel mq bundle demo as example-camel-mq.bundle so that example-camel-mq uses just the mq-fabric-camel component ("amq") and a camel route in the profile; so its clean, lean and mean!
Only wait for provisioning if agent is enabled. Remove low level OSGi APIs for waiting on FabricService and use DynamicReference instead.
[FABRIC-524] Fix mq distribution test.
Add headers to MQTestSupport.
Test that after fabric is created in the MQ distro the service is properly published.
Remove out.println message is FabricDiscoveryServlet.
Test failover after gracefull shutdown of containers.
Add zk:kill command for kill the current zookeeper session.
[jboss-fuse-6.1.x 129] Updating perfectus-build number to new build