This component is not yet available in our repository. We are in the process of creating CQs for the required third party code and hopefully get permission to use it in our project.
Located in bundle: org.eclipse.smila.aperture
This service implements the MimeTypeIdentifier interface using the "magic" identification functionality of Aperture. The service uses either the document's content (a byte), a file extension or both. For best results it is recommended that you use both (input data and extension) to identify the mime type of the data, since the aperture mime type identification mainly focuses on the magic numbers in the file and so often fails to determine e.g. office documents' mime types when no conten is given.
The javadoc for the implemented interface can be found here.
To enable the service, start bundle org.eclipse.smila.aperture and get a OSGi service reference for interface org.eclipse.smila.common.mimetype.MimeTypeIdentifier. You should take care not to start the org.eclipse.smila.common.mimetype.impl bundle to ensure that the Aperture based implementation is used and not simplistic one that SMILA provides as a fallback. We have set the service rankings of those services such that the Aperture implementation should be preferred if both are running, but it's always better to be sure what happens in your system ;-)
Interaction with the MimeTypeIdentifyPipelet
When the Aperture based MimeTypeIdentifier is started, it uses the org.eclipse.smila.processing.pipelets.MimeTypeIdentifyPipelet automatically (if no other MimeTypeIdentifier service with yet a higher service ranking is active, of course).
For information on how to configure the mime type identification pipelet, which uses the MimeTypeIdentifier service to recognize attachment mime types please refer to MimeTypeIdentifyPipelet.