From IRC:(09:41:33 AM) janstey: gtully, dejanb: do you guys know why we are not using blueprint for the broker in MQ?
(09:42:14 AM) dejanb: janstey: we have our own broker factory
(09:42:28 AM) dejanb: controlled using config admin
(09:42:52 AM) dejanb: so we can have more control over broker groups/disocery/master-slave
(09:44:11 AM) janstey: wondering where to export the ConnectionFactory now though - in the past we just had a OSGi service element in the broker blueprint file
(09:44:31 AM) janstey: i think folks will be expecting to have that available as we are in a OSGi container
(09:44:44 AM) dejanb: janstey: we have mq-client
(09:44:47 AM) dejanb: bundle
(09:45:04 AM) janstey: that exports the CF?
(09:45:07 AM) dejanb: that contains some basics for clients
(09:45:17 AM) dejanb: i need to recheck ... but it should
(09:45:22 AM) janstey: ah ok cool
(09:45:26 AM) dejanb: activemq example is based on that
(09:45:36 AM) dejanb: and it uses fabric discovery to find broker
(09:45:43 AM) janstey: just thinking of camel where we always just grab a ref to the CF OSGi service
(09:45:50 AM) dejanb: so I guess we should add there if anything is missing
(09:53:50 AM) janstey: yep, client doesn't export any CF
(09:54:13 AM) dejanb: damn ... can you raise a Jira for it
(09:54:14 AM) dejanb: ?
(09:54:22 AM) janstey: yep, sure thing
(09:54:26 AM) dejanb: cheersWill hold off on ENTESB-124 until this is done so folks can still use the local ESB broker in the same was as always (i.e. grab a ref to the CF via OSGi).