https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
Mark Thomas changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
--- Comment #4 from Mark Thomas ---
(In reply to Andrei Ivanov from comment #3)
> I remember having a problem with AOP and load time weaving where Tomcat was
> scanning the WAR for servlet annotations and caching the classes so by the
> time
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
--- Comment #3 from Andrei Ivanov ---
I remember having a problem with AOP and load time weaving where Tomcat was
scanning the WAR for servlet annotations and caching the classes so by the time
the app was starting and LTW enabled, the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
--- Comment #2 from Mark Thomas ---
Leaving this open for now but it will be closed as WONTFIX if no justification
for caching classes is provided.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--
You are receiving this
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
--- Comment #1 from Mark Thomas ---
It is expected that a class file is read once and once only when the class is
loaded into memory. Therefore there is no point caching the contents of a class
file.
What use case requires that classes are
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
Alexandr changed:
What|Removed |Added
Hardware|All |PC
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685
Alexandr changed:
What|Removed |Added
Severity|normal |major
--
You are receiving this mail
