Can you show up the entire class ?
François Meillet
Formation Wicket - Développement Wicket
Le 20 déc. 2014 à 09:56, Satrix <satrix...@gmail.com> a écrit :
> Hi,
>
> It would be quite hard to reproduce the problem in quickstart application.
> Here is the code of DynamicImageResource:
>
> @Override
> protected byte[] getImageData(IResource.Attributes attributes) {
> try {
> return IOUtils.toByteArray(stream);
> } catch (IOException ex) {
> LOG.error("Could not return byte[] from " + stream, ex);
>
> return null;
> } finally {
> if(stream != null){
> try {
> stream.close();
> } catch (IOException ex) {
> LOG.error("Could not close stream", ex);
> }
> }
> }
> }
>
> And then I use the NonCachingImage in conjunction with my
> DynamicImageResource implementation class.
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Possible-memory-leak-in-Wicket-1-5-12-tp4668856p4668863.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
