Community
Participate
Working Groups
Following investigation into bug 179685 we found that JavaCore.newLibraryEntry() has a very high invocation count during startup when considering EEs with access rules - see profiling screen shots on 179685.
Michael, I'm not sure to understand what you expect from us. JDT/Debug is making all these invocations, isn't it ?
yes we are, we were thinking (hoping) that there would be some way that we could batch or cache already created entries to be reused. Although as each access rule participant can create custom rules per project this seems unlikely.
we'll take this one back, as it has to do with us not you guys :)
The way the current API stands there is nothing we can do about this. To cache entries we need a compound key something like (vminstall, rules, environmentid) -> classpath entries which would be sufficient, but each query to an EE for its rules creates a new array of rules (as the rules are collected from all of the participnats at the time the request for the rules occurs), therefore we can not effectively compare the arrays of rules for equality (using == ) without incurring more work than is already done. There is no way to batch create libraries. marking as WONTFIX, since realistically there is nothing we can do....
