Difference between revisions of "SMILA/Documentation/ApertureMimeTypeIdentifier"

From Eclipsepedia

Jump to: navigation, search
m (Description)
 
Line 1: Line 1:
<span style="color:#ff0000">'''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.'''</span>
+
<span style="color:#ff0000">'''This component is not available as we have switched from Aperture to Tika.'''</span>
  
 
== Class: <tt>org.eclipse.smila.aperture.ApertureMimeTypeIdentifier</tt> ==  
 
== Class: <tt>org.eclipse.smila.aperture.ApertureMimeTypeIdentifier</tt> ==  

Latest revision as of 06:57, 11 January 2013

This component is not available as we have switched from Aperture to Tika.

[edit] Class: org.eclipse.smila.aperture.ApertureMimeTypeIdentifier

Located in bundle: org.eclipse.smila.aperture

[edit] Description

This service implements the MimeTypeIdentifier interface using the "magic" identification of MIME types in Aperture. The service uses either the document's content (a byte[]), a file extension or both. For best results, it is recommended to use both input data and extension to identify the MIME type of data, since the MIME type identification of Aperture mainly focuses on the magic numbers in the file and so often fails to determine e.g. office documents' MIME types when no content is given.

For further information on the MIME type extraction in Aperture please consult the respective documentation pages (e.g. MIMETypeIdentification).

The JavaDoc of 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 ;-)

[edit] 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 the MIME types of attachments please refer to MimeTypeIdentifyPipelet.