james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-174) Refactor org.mime4j.util.CharsetUtil to lazily determine supported encodings/decodings
Date Thu, 04 Mar 2010 21:21:27 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841527#action_12841527

Stefano Bagnara commented on MIME4J-174:

Linking this one to MIME4J-159 as this issue is probably fixed moving to java5 Charset methods.

> Refactor org.mime4j.util.CharsetUtil to lazily determine supported encodings/decodings
> --------------------------------------------------------------------------------------
>                 Key: MIME4J-174
>                 URL: https://issues.apache.org/jira/browse/MIME4J-174
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>            Reporter: Richard von Keyserling
> On initialization CharsetUtil determines all supported endcodings and decodings by attempting
to encode and decode a dummy string with every entry in JAVA_CHARSETS.   This loads a lot
of classes into the JVM which in turn uses up a lot of permGen.   
> Moving the decoding and encoding tests into isDecodingSupported() and isEncodingSupported()
and adding positive results to the decodingSupported and encodingSupported treeSets from those
methods would allow the class to only load encoders and decoders the application needs. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message