Thanks Kris. Very valuable information indeed.
I like the filter idea, or as one of the links you listed suggests, a
context listener would also do the trick.
Personally, I have nothing against reflection, in fact, I think it's one
of the greatest features ever, but when it comes to constants,
Thanks a lot Luca for pointing this out. I must say it's completely new
information to me. I wonder if it's really accurate and relevant to all
containers.
For example, in Oracle Containers for Java (OC4J), when you redeploy an
application, the OC4J instance is restarted. You can reload an
Tarek Nabil wrote:
Thanks a lot Luca for pointing this out. I must say it's completely new
information to me. I wonder if it's really accurate and relevant to all
containers.
For example, in Oracle Containers for Java (OC4J), when you redeploy an
application, the OC4J instance is restarted.
The implication that the example singleton class causes a memory leak just
because ...it creates a hard reference to a class instance into the class
itself is hard to believe. There are plenty of other ways to pin classes
loaded by the web app's class loader, but the singleton pattern isn't one
