ComponentRender#destroy() destroys the application, there's not much
more to it.
In most cases you will want to reuse the application for performance
reasons. A specific application can even be used as constructor
argument, which might be the main web application that you don't want to
be destroyed prematurely.
So auto-closing i.e. destroying the renderer after each render might
lead people into the wrong direction.
On 24.05.20 16:28, Thorsten Schöning wrote:
I'm using Wicket as a template engine to render reports in some
backend with various different output formats. Everything is based on
"ComponentRenderer", though, and that introduced a large memory leak
in my case. Root cause simply was that I forgot to call "destroy".
So how about implementing AutoCloseable by that class? In most IDEs
that would have at least triggered a warning.
Mit freundlichen Grüßen,