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.
