You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Daniel Spicar (JIRA)" <ji...@apache.org> on 2012/08/31 18:14:07 UTC

[jira] [Resolved] (CLEREZZA-716) Support alternate image processing libraries for reading image data

     [ https://issues.apache.org/jira/browse/CLEREZZA-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Spicar resolved CLEREZZA-716.
------------------------------------

    Resolution: Fixed
    
> Support alternate image processing libraries for reading image data
> -------------------------------------------------------------------
>
>                 Key: CLEREZZA-716
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-716
>             Project: Clerezza
>          Issue Type: Improvement
>          Components: platform, rdf.utils
>    Affects Versions: 0.2-incubating
>            Reporter: Daniel Spicar
>            Assignee: Daniel Spicar
>            Priority: Minor
>          Time Spent: 12.5h
>  Remaining Estimate: 0h
>
> Currently clerezza uses Java Image IO to read images and create BufferedImages. This is done in various places such as the ImageMetaDataGenerator and the AlternativeRepresentationGenerator. However the Java ImageIO implementation can fail with some JPEGs that have certain meta data stored that does not conform exactly to JPEG specification. In order to handle such cases there should be a possibility register other libraries or implementations that generate BufferedImages and handle these cases.
> I suggest to create a BufferedImageProvider OSGi service and use it in the meta data generators mentioned above. There should also be a default implementation of this service that uses Java ImageIO. Clients should then be able to register services that override this service and may have different implementations that return BufferedImages. I think it might work with the service-ranking property but I am not sure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira