[
https://issues.apache.org/jira/browse/XBEAN-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432900#comment-13432900
]
SheldonShao commented on XBEAN-208:
-----------------------------------
This cache has huge improvements for the performance of class loading.
However, if the class is not found in any bundles.
The performance still worse for this situation.
There are too situations will cause invalid class loading calling.
1. JDTCompiler try loading a class with package name to make sure the name
wasn't used by class.
For example, it tries to loading class "org/apache/class" for package
"org.apache".
This causes many invalid class loading.
2. Another issue is from Introspector.getBeanInfo. It tries three kinds of
class names to loading BeanInfo for a class.
Also, it causes many invalid class loading.
> DelegatingBundle performance issues
> -----------------------------------
>
> Key: XBEAN-208
> URL: https://issues.apache.org/jira/browse/XBEAN-208
> Project: XBean
> Issue Type: Improvement
> Components: bundleutils
> Affects Versions: 3.11
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> DelegatingBundle suffers from some performance issues when loading classes or
> looking up resources.
> The getResource() can be slow because each lookup can cause a lookup on each
> bundle that DelegatingBundle delegates to.
> The loadClass() can be slow for the same reason as getResource() and because
> PackageAdmin (which can be very slow) is used to lookup a bundle for a given
> package.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
