You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by "simon steiner (Jira)" <ji...@apache.org> on 2019/09/23 14:02:00 UTC

[jira] [Resolved] (BATIK-1203) ImageTagRegistry forgets to reinitialize cache

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

simon steiner resolved BATIK-1203.
----------------------------------
    Resolution: Fixed

http://svn.apache.org/viewvc?view=revision&revision=1867375

> ImageTagRegistry forgets to reinitialize cache
> ----------------------------------------------
>
>                 Key: BATIK-1203
>                 URL: https://issues.apache.org/jira/browse/BATIK-1203
>             Project: Batik
>          Issue Type: Bug
>            Reporter: Erich Schubert
>            Assignee: simon steiner
>            Priority: Major
>
> Pull request is here:
> https://github.com/apache/batik/pull/4
> ImageTagRegistry fails to clear the cache via:
>   extensions = null;
>   mimeTypes = null;
> whenever entries are NOT inserted in descending priority. Only if the "if" condition never triggers the cache is correctly reset.
> The reason why this went largely unnoticed is that when the entries are loaded initially, the cache is still null. So it usually gets initialized only once. But because of this bug, you cannot later register a higher-priority handler yourself.
> To test, make sure the cache is populated before calling "register". Then register a low priority entry.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org