Backups/TwelveMonkeys
2
0
Fork 0
mirror of https://github.com/haraldk/TwelveMonkeys.git synced 2025-08-04 03:55:28 -04:00
Code Issues Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/master'

Browse Source
This commit is contained in:
Harald Kuhr 2017-04-19 20:47:10 +02:00
commit acf7c5f007
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -94,7 +94,7 @@ Alternatively, if you have or know of a JPEG-2000 implementation in Java with a
* CMYK, 4-5 channels, 8, 16 and 32 bit * CMYK, 4-5 channels, 8, 16 and 32 bit
* Read support for the following compression types: * Read support for the following compression types:
* Uncompressed * Uncompressed
* RLE (PackBits)< * RLE (PackBits)
* Layer support * Layer support
* Image layers only, in all of the above types * Image layers only, in all of the above types
* Thumbnail support * Thumbnail support
@ -365,7 +365,7 @@ Because the `ImageIO` plugin registry (the `IIORegistry`) is "VM global", it doe
servlet contexts. This is especially evident if you load plugins from the `WEB-INF/lib` or `classes` folder. servlet contexts. This is especially evident if you load plugins from the `WEB-INF/lib` or `classes` folder.
Unless you add `ImageIO.scanForPlugins()` somewhere in your code, the plugins might never be available at all. Unless you add `ImageIO.scanForPlugins()` somewhere in your code, the plugins might never be available at all.
I addition, servlet contexts dynamically loads and unloads classes (using a new class loader per context). In addition, servlet contexts dynamically loads and unloads classes (using a new class loader per context).
If you restart your application, old classes will by default remain in memory forever (because the next time If you restart your application, old classes will by default remain in memory forever (because the next time
`scanForPlugins` is called, it's another `ClassLoader` that scans/loads classes, and thus they will be new instances `scanForPlugins` is called, it's another `ClassLoader` that scans/loads classes, and thus they will be new instances
in the registry). If a read is attempted using one of the remaining "old" readers, weird exceptions in the registry). If a read is attempted using one of the remaining "old" readers, weird exceptions