Allow dispatching of binaries to different storage

Binary managers are now configured explicitly from a separate extension point, and by default (unless a specific Blob Dispatcher is registered), each repository uses the binary manager of the same name as the repository: <extension target="org.nuxeo.ecm.core.blob.BlobManager" point="configuration"> <blobprovider name="default"> <class>org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager</class> <property name="path">binaries</property> </blobprovider> </extension> Choosing where a blob is stored based on blob or document properties is now possible through the use of a Blob Dispatcher. The DefaultBlobDispatcher can be configured using properties to choose a different blob provider (binary manager). Example configuration: <extension target="org.nuxeo.ecm.core.blob.BlobManager" point="configuration"> <blobprovider name="videos"> <class>org.nuxeo.ecm.core.blob.binary.DefaultBinaryManager</class> <property name="path">binaries-videos</property> </blobprovider> <blobdispatcher> <class>org.nuxeo.ecm.core.blob.DefaultBlobDispatcher</class> <property name="dc:format=video">videos</property> <property name="blob:mime-type=video/mp4">videos</property> <property name="default">default</property> </blobdispatcher> </extension> The DefaultBlobDispatcher javadoc has details about the syntax of the property name. It can be subclassed to provide more flexible logic