Seems like we get a fabricService even when we are not yet connected to fabric.  Trap exceptions and assume we are not part of a fabric.  Should fix up stand alone a-mq distro startup issues.
avoid eager deletion of the class files for easier introspection
Added repository support
Actually this is a better fix than the previous commit.
[jboss-fuse-6.1.x 028] Updating perfectus-build number to new build
[jboss-fuse-6.1.x 029] Updating perfectus-build number to new build
ENTESB-807: Upgraded to jolokia 1.1.3
fixes #44 so that we can use the FileWatcher to find spring XML files and start/refresh/stop them based on file system edits; such as using the wiki and hawtio to edit camel routes in a regular web app
 #44 adds support for watching and dynamically adding/updating/removing blueprint containers while watching the file system; so folks can edit blueprint based camel XML files on the fly in the hawtio wiki
 #44 explicitly filter out any matched XML files which don't contain the correct namespaces to avoid generating unnecessary exceptions in the log if we try and parse arbitrary XML files as spring or blueprint
Avoid possible NPE
Upgrade to pax-web 3.0.2
FABRIC-501: Need another Camel EA build to reuse camel-dozer better.
 #44 allow the parent container to be registered; so one day we can use it to auto-default the properties and class loader
Improve fabric core service registration.
refactored the various watcher related modules to use a common "watcher-" prefix so its a bit more obvious they are related
Now that the fabric service is not registered in OSGi until it's configured, we can simplify things a bit.
Disable ensemble.auto.start flag, when ensemble is started.
#45: Allow advertising a different port (than the binding port) for http, jmx, ssh and zookeeper.
removed imports