[
https://issues.jboss.org/browse/JASSIST-150?page=com.atlassian.jira.plugi...
]
Bruce Garner commented on JASSIST-150:
--------------------------------------
Yes - under one circumstance caching isn't working.
If you have a look at the attachement I uploaded earlier today you can see some minor
changes to the caching which I believe makes the caching simpler. It places the logic of
what to cache closer to the cache.
I have run the junits with these changes and they all work and I'm doing the same on
our entire project currectly to see that all the junits work.
Performance problem with loading classes under certain circumstances
--------------------------------------------------------------------
Key: JASSIST-150
URL:
https://issues.jboss.org/browse/JASSIST-150
Project: Javassist
Issue Type: Enhancement
Affects Versions: 3.15.0-GA
Reporter: Bruce Garner
Assignee: Shigeru Chiba
Attachments: Jassist150.java, Javassist150src.zip
There is a performance problem in the class loading in javassist. Under certain
circumastance the parse of the code will mean that javassist will attempt to load classes
starting at the base of the package, and get failures for the package base until it finds
the class. There is no caching of this failure so each attempt to load the class searches
the entire classpath and fails.
Unfortunately the code in PowerMock exercises this bug, and in large systems with may
items on the classpath, large numbers of classes and large classes the process can be
slow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira